I've had a coffee from a high end bean to cup machines, installed in a conference room at our vebdor's headquarters, which used fresh milk and made a better cappuccino than I've had from real humans at many chain coffee shops. They might be rare, but they're out there.
Bit of a mixed bag for me. There are a lot of things that work remarkably well, but I have some issues with GPU performance (Cyberpunk 2077 just doesn't run well on Linux for me, despite running great on Windows on the same PC, and GPU-heavy apps like Insta360 Studio and Topaz Denoise run excruciatingly slow or not at all) and some things just don't work (my audio VST plugins work alright, albeit with some bugs about window position handling, but I can't get some of the licensing apps to work under WINE).
I'd prefer to run Linux, but one of my two primary dev targets requires a proprietary Windows IDE (Automation Studio by B&R). So running that on Windows then using WSL to develop for my Linux servers is the easy path.
I really like Darktable, and it's my go to photo editor, but the user interface really isn't intuitive on first look compared to something like Lightroom. The design choice that editing modules should be ordered by their place in the pixel pipeline is logical and sometimes useful, but it ends up with a lot of the controls being in rather weird places. The customisable quick controls palette would help, if it weren't that simple things like cropping can't be added to it (at least, last time I investigated this - perhaps it's changed now?)
I could have been clearer. I wouldn't say it's the paragon of photo editing, but it's further along in terms of usability. I've seen some normal people who don't want to pay the Adobe tax move to it.
An investigation of FOSS development would highlight a bunch of problems that exist to a lesser extent with other software development. When money is on the table and there is no motivation to keep supporting behaviors that particular contributors favor then feedback shift things. When you're building stuff for "yourself" then that feedback doesn't land the same even if the project owner has aspirations for better UX.
Unfortunately, vintag.es does seem to have done some work here - while they copied the text, they also added several more images to the single image in the original post.
Hah, damn. We live in different worlds - in mine, 100K samples/sec is blazingly fast!
I'm currently working on a PLC program, replacing the PLC's basic cyclic input sampling (max 2K samples/sec) with a harder-to-use mechanism that lets you access the raw data off its 12-bit ADC at 10K samples/sec, which we consider unusually speedy.
Some of my code gets deployed to a PLC aboard a wave power generator hundreds of metres offshore, with a cellular link that might go down in a storm. If something gets unrecoverably wedged, retrieving the device starts at $10K to hire a ship.
Wow, that's a fantastic and terrifying example. "Retrieving the device starts at $10K" is about as high-stakes as it gets for software reliability. It perfectly crystallizes the difference between rebooting a cloud instance for pennies and the extreme costs of failure in the physical world.
reply