JBOD relies on an optional SATA extension, which most of your controllers won't have.
That leaves you with RAID in the controller - which is a bad idea, as you don't have much control over what is going on, and recovery if it fails will possibly messy.
Mobile workstation. There are some Xeon notebooks which also can take more than 64GB - but they have bad availability, cost about the same as a high end mac book pro, are significantly larger and heavier, run hot and have shitty battery life for comparable performance.
The overall hardware situation has been ridiculous for many years now. I recently got a new Dell Latitude for a customer project - runs hot, performance and runtime suck. Runs out even faster than my tiny GPD pocket 3, while providing worse performance. Compared specs - they indeed stuck a smaller battery into the business notebook than into the portable toy. We're now at a point were a Chinese niche hardware maker does better thermal management for x86 systems than any of the established manufacturers. Current AMD mobile CPUs are great - and I'd love to have a good notebook with one, just nobody bothers building it.
AMD can compete in performance and power/Watt mid to high load, but is shit with low load efficiency. intel has nothing at all. Apple scales nicely over the complete range.
If you want a relatively small notebook with lots of RAM you also don't have options (not really AMDs fault, but hardware manufacturers seem to produce mostly shit now). Framework is pretty much the only somewhat decent option with 64GB max, if you want more there's pretty much only apple - which is way overcharging for that.
Microsoft is trying the same - but royally screwing up how they deal with hardware partners. Performance wise the snapdragons they use are roughly a decade behind what Apple is doing - I have both systems for work projects.
The x86 emulation in Windows is imo better solved than rosetta - but the rest of the stack is a mess. For example, the deployment tools only got arm support a few months ago.
And Linux support on those things sucks - while using it on the M1 is great.
As they just want it temporarily lubed water based lubricants from the sex shop might be a better option. They don't leave much residue, and are tested for compatibility with various rubbers.
You still might want to do something like alias pbtar='tar --use-compress-prog=pbzip2 to easily use pbzip2 - unless you have an ancient system that'll speed things up significantly. And even if you don't it'd be nice to use it for creation - to utilize more than one core the archive needs to be created for parallel extraction.
They've shown over and over again over the last years that they're happy to push arbitraty lies for whatever reason. NY Times is probably one of the few newspapers where replacing the journalists with chatgtp would increase quality and factual accuracy.
I just tried to sign up there, but seems they only accept stripe as payment - which still insists on making me solve unsolvable captchas before letting me pay.
I should have 3 different glow filaments somewhere, one PETG, two PLA. Typically I preferred the PLA versions - they had a bit more uniform glow. The PETG one had brighter spots, but as it was mostly transparent individual spots were more visible than with the PLA prints.
RCS is just stupid. When I was still building phones a decade ago we had some operators ask for it - but after reading the standards decided to just ignore it and hope it passes. Pretty much everybody did that, until google got interested - presumably because they figured it'd be a good way to get control of messaging on a lower level. As that's exactly what RCS is: control of messaging, and ideally the option to charge for it, just like SMS and MMS before that.
They used to link to my dig wrapper on my homepage for having their clients debug DNS problems for many years - even with translations of my UI in the various language help sites. I always found it amusing that a hoster of their size does that, instead of spending a lunchbreak to throw something together that integrates with their help page.
There also was a non significant number of users which didn't understand that my homepage had nothing to do with OVH, and ended up mailing me about their DNS problems.
That's a feature, not a bug. His family got rich with mines in south africa, exploiting the locals. For getting more rich by mining mars you'll have to bring your own locals to exploit, and there's no need to make it to comfortable for them.
They're in a lot of government networks world wide (I visited them a long time ago to discuss some potential cooperation) - they're technically quite sound, and as bonus them being privately owned and headquartered in small Finland is generally seen as reducing the likelihood of backdoors or similar issues due to conflicting state interests.
Because it does JBOD if the controller supports it. Pretty much none of the controllers you'll find in consumer hardware support that.