qupada

That's a big part of the problem though... it's Unix. The BSD-based underpinnings of Mac OS are just different enough to be a colossal pain in the arse for interoperability with GNU-based systems.

At a surface level things seem similar enough, but that people seem to think developing on Mac and deploying on Linux is this simple process really confuses me, because every time it's come up in my career nothing has ever worked properly. Every occasion a bunch of time wasted finding the one little difference that breaks on one platform (and I'm going to be blunt here; it was always on the Mac).

For my money too, the Mac UI features some of the most incomprehensible and borderline unpleasant design decisions. Window management is downright infuriating. File management feels barely functional. Apple's stubborn insistence in hiding the options they'd clearly prefer you didn't use (to make using it actually pleasant) in "accessibility" menus is baffling.

Some of this stuff harks back to last century. I hated the way things worked back then in Mac OS 6 on a Mac classic, and a lot of it they still haven't fixed.

Often it's attached to a motor, but the pointy end hasn't changed much.

Certainly juicing the likes of apples or carrots warrants a different kind of appliance, but squashing citrus is a fairly solved problem.

35% is the kind of numbers I used to have on servers at work, which often feature >2TB of RAM.

(another similar percentage being the CPUs, 128 cores per socket doesn't come cheap)

Seeing those numbers for desktop hardware, "holy fuck" is about right.

You wrote this all a lot better than I could have, but to expand on 2) I have no desire whatsoever to have a "conversation" (nay, argument) with a machine to try and convince/coerce/deceive/brow-beat (delete as appropriate) it into maybe doing what I wanted.

I don't want to deal with this grotesque "tee hee, oopsie" personality that every company seems to have bestowed on these awful things when things go awry, I don't want its "suggestions". I code, computer does. End of transaction.

People can call me a luddite at this point and I'll wear that badge with pride. I'll still be here, understanding my data and processes and writing code to work with them, long after (as you say) you've been priced out of these tools.

Not that I know of, which means I can only assume it'll be a timing-based attack.

With strategic use of sleep statements in the script you should stand a pretty good chance of detecting the HTTP download blocking while the script execution is paused.

If you were already shipping the kind of script that unpacks a binary payload from the tail end of the file and executes it, it's well within the realm of possibility to swap it for a different one.

Magimix are French, and may be the high-quality product you seek.

I upgraded from a Kenwood which was good enough, but the upgrade to direct-driven and an induction motor was substantial (as is the weight of the unit).

Their commercial products are sold under the name "Robot Coupe", I see those show up used from time to time (usually when a restaurant goes out of business) so that could also be an option.

DVDs didn't have that issue, fortunately.

In CDs, the recorded layer is directly under the label, in DVDs it's mid-way through the thickness of the disc so there's a layer of plastic between it and the label. A function of different wavelengths of light used to read them.

Bit rot due to degradation of the organic chemicals in the recording layer is still very much a concern though.

That, or the aspiring rich arsehole.

Not even a beneficiary, just a grossly misguided individual who hasn't yet realised that will, in fact, not be them some day.

"Method and apparatus for insufflation of oxygen into a body by means of flexible permeable membrane"

Thoughts and prayers 🙏

Frankly an average tortoise has a good chance of outliving your grandchildren.

150 years is not an unreasonable upper bound for their lifespan, for the larger species.