For sure! I think we're going to have to move away from a one-size fits all car design. For general city use, I use a Chevy Bolt, but for longer (infrequent) runs, I'm still stuck with ICE (I'd use a hybrid if I had one). In Canada, the range really does go down in the winter. (and Canada has not taken charging infrastructure very seriously - mandatory for adoption)
Anyway you look at it, these are very, very positive developments.
The key is that with the right use case, it frees up lithium to be used where only it is suitable.
(for my needs I'd be fine with sodium...)
At most, you might be able to get midi mode to work (if you scrounge the internet for experimental and old reverse engineered scripts.) But almost certainly not the core Maschine functionality (ie - the main reason for buying maschine in the first place).
Even if you can get it to work none of it will be supported and you're always at risk of an update rendering things inoperable.
It's worth noting that only the old Native Access installer runs in wine (with coaxing). The newer one does not, and from what I've read, the break points are features that will never be supported in wine.
Wine is clever, but it's always an incomplete game of whackamole. A workaround at best.
The whole thing is truly frustrating.
(your luck may be better than mine of course!)
The Adobe case is a big one. For me, it's lightroom that has no real Linux counterpart. The app itself isn't where the magic is - darktable exists. The magic is in the interapp interoperability - bi-directional syncs and edits in any platform. FOSS is very unlikely to create something like this (would love to be wrong) as it's less of a tech challenge than an enterprise architecture challenge with a component systems falling in line. This sort of thing requires money to be executed effectively, unfortunately.
Really hope overall user base in Linux can grow enough to catch attention of SW/HW manufacturers, but have been hoping this for many, many years...
For me, it's not the DAW (Reaper works fine), but this is not the case for every DAW and it must be recognized that switching DAWs is non-trivial (nor should it be expected). In my case, it's the HW. I can likely get my interface to run (unsupported) but my Maschine is a non-starter. Yes - I know there are a few drivers for similar HW around written by clever folk who've done reverse engineering, but it only covers a few minor use cases and is, at best a science experiment and not something one should ever depend on even if it did work.
SW is a problem too - yes most plugins can be coaxed into working, but certainly not all. Add to that the underlying tech is usually wine, and it's a perpetual game of whackamole to maybe get the stuff you paid for to run.
The folks writing these bridging tools are not too blame - it's brilliant, wonderful work. Fundamentally, it's an act of good will that one can't rely afford to fully depend on if it even does work. I love FOSS, but it's not everything - I certainly don't expect a free ride, but I do want the option to pay to run what I want.
The issue is the HW and SW manufacturers - they need a critical mass of potential users to be bothered to commit to developing for Linux. My hope is that as user bases grow (in places like India) the cost/benefit analysis shifts.
Dang... Was hoping to kill two birds with one stone and solve that space elevator thing too...
/s
Exactly. Personally, I'm relegated to Windows with a healthy dose of WSL. Wish it weren't so, but it is so.
For me, it's the lack of support for the audio HW. Infuriating.
Since Twitter has nothing to do with Tesla (beyond the emotionally stunted owner) this is serious line being crossed. I mean - I don't care about Tesla. But I do care about SpaceX and Starlink as they have serious geopolitical implications.
Some country's leader disses Twitter and they don't get to launch satellites. Or their people don't get satellite internet.
This amount of power should not be in the hands of one rich guy with an inferiority complex.
My concern (back then) with keeping the greens spun up would be that I'd lose the energy savings potential of them without the benefits of a purpose built NAS drive.
In my current NAS, I just have a pair of WD Red+. I don't have a NVME cache or anything but it's never been an issue given my limited needs.
I am starting to plan out my next NAS though, as the current on (Synology DS716+) has been running for a long time. I figure I can get a couple more years out of it, but I want to have something in the wings planned just in case. (seriously looking at a switch to TrueNas but grappling with price for HW vs appliance...). My hope is that SSDs drop on price enough to make the leap when the time comes.
I had WD Greens in my first NAS (they were HDDs, though). This was ill-advised. Definitely better for power consumption, but they took forever to spin up for access to the point where it seemed like the NAS was always on the fritz.
Now I swear by WD Red. Much, much better (in my use case).
(I'm not sure how things pan out in SSD land though. Right now it's just too pricey for me to consider.)
This is very good. The higher those numbers go, the more pressure there will be for better official support for both HW and SW.
FOSS is fantastic. But lack of options (FOSS or paid) for a few of my use cases keeps me stapled to Windows and WSL. Unfortunately. I'm hoping the momentum shifts.