How long
0 minutes ๐คญ
avidamoeba
joined 1 year ago
This is awesome.
Different cores, different topologies, different interconnects, different memory throughputs... fahgedabouddit.
ARM on Mac isn't nearly as helpful for workloads on an ARM server as x86 PC for an x86 server. The differences in hardware behavior between the two x86 parts is small because the platforms are standardized way beyond the instruction set. The ARM server on the other hand has nothing to do with the Mac beyond the instruction set. Something runs great on your Mac because of the on-SoC ridiculously fast RAM. You throw it on an ARM server with completely different ARM CPUs, slotted RAM and a bottleneck shows up.
And that underlying stuff doesn't run the same on x86 and dog knows who's ARM implementation.
Zipties and brown for life.
It's supremely useful if you want to use Google search. If you don't on the other hand... ๐ฅฒ
How many clicks does it take to change the search on the home screen?
The best sequence.
Probably not for organizations given they depend on the device management functionality that comes with Chromebook. If they're to switch to another OS, they'll have to take on this device management. Roll their own timely security updates, hardening, content filtering, security policy creation and provisioning, privacy compliance, you name it. All of this and more done by every org. Chromebooks aren't merely just a bunch of hardware. Their value proposition leans heavily on the OS and the built-in support and device management features.
The right way (tm) is to have the application deployed with high availability. That is every component should have more than one server serving it. Then you can take them offline for a reboot sequentially so that there's always a live one serving users.
This is taken to an extreme in cloud best practices where we don't even update any servers. We update the versions of the packages we want in some source code file. From that we build a new OS image contains the updated things along with the application that the server will run and it's ready to boot. Then in some sequence we kill server VMs running the old image and create news ones running the new. Finally the old VMs are deleted.
What you're asking for is a monopoly. It rarely is cheaper or easier. Sometimes, when heavily regulated, it could be. But history shows most of these are eventually privatized and deregulated and then we know what happens.