on-device processing is still a thing
Unfortunately even if this is initially processed locally, there’s a significant risk that results and/or samples are still sent back. manufacturers have shown on multiple occasions that the allure of data they can leverage is too much to resist.
Physical buttons have wiring harness failure, mechanical failure, and software failure…pretty much exactly the same amount as the touchscreen solution.
What boggles my mind is that cheap, snappy, easy-to-use touchscreen interfaces have been a solved issue for well over a decade with the proliferation of smartphones…why the hell do car manufacturers suck so much at implementing it!? They’re all slow bug-ridden shitshows.
According to Phoronix, Ampere’s new CPUs have so many cores that Linux doesn’t support systems when two of Ampere’s 192-core chips (384 total cores) are installed in a single server. For now, the ARM64 Linux kernel only supports systems with 256 cores or less. To fix the issue, Ampere has submitted a patch proposing that the Linux kernel core limit be raised to 512
If you’re already at 384 cores in a dual-processor setup, isn’t raising the limit to 512 too little? Why not just go for 1024 now that they’re at it, especially since the method they proposed doesn’t increase kernel image memory footprint.
Blender is not CAD software though, it’s 3D modelling software. They’re not quite the same thing, and they’re intended for (and excel at) different things.