Unfortunately it is a bit more complicated than that. All these phones run firmware, bootloaders, libraries under license from SoC providers, who package components from other vendors under a license themselves. Opening up the bootloader can be done, but two things have to happen: either the phone is crippled of various functionalities or the manufacturer is in breach of license because all the binary blobs become open and can be reverse engineered. No one wants to go through all of this for a few hundred people who are interested in running their home assistant on an exotic device.
I haven't ever heard of an SoC supplier demanding that the device's bootloader must be locked. Are you sure that this is happening? I've only ever seen devices delete first-party blobs, presumably of the manufacturer's own volition.
When cores start needing more than 9 bits to be represented and RAM is in terabytes, many of the old assumptions need to change. Schedulers need to be implemented in userspace, RAM needs to be allocated in GB, not in 4k, io needs to require less round-trips between kernel and user space and NICs need to do a lot more work before the data reaches the CPU.
Does it need to be the same OS? Most consumer device are in the low 16GB range for memory with some outliers in the 64 and 128 GB. 32 cores are still in the realm of specialized devices.
Yes, we’re not the one paying for Linux development, but its subsystems are so complicated for general purpose computing. Like fitting formula 1 car parts onto a camry.
Our software is littered with the consequences of these kinds of assumptions, and they have an impact on consumer use cases.
x86 still runs in real mode on boot despite dropping the PC BIOS.
Lots of software still assumes a 4kb page size, to the point where migrating Android to 16kb is an ongoing multi-year effort involving far too many people. And this is an OS for phones, which you might assume would lack the memory to benefit from a larger page size.
And one of the most popular consumer CPUs for enthusiasts, the Ryzen X3D chips, broke assumptions in both Linux and Windows schedulers that all cores have access to the same amount of L3 cache.
I would probably not assume the kinds of hardware limitations that we have now will persist into the useful lifetime of current software. Splitting the OS into "consumer" and "enterprise" variants is one of those moves that would bake in a ton of assumptions and make things messier in the future.
It’s all about contracts. It’s fine to define assumptions and build software on top of those. It’s also fine to break those and adjust the software. The trap is trying to steer towards a universal solution (Yagni is the cure there) or trying to slip something in that does not respect the contracts (hence bugs).
UEFI could have supported something like ELF and do away with real mode. Intel and Amd could have just introduced a new line of cpu and everyone could have transitioned to that (with maybe shims to soften the change). But everyone is all about backwards compatibility and compile once, runs for eternity.
If we are successful building an "ultra" human AI, it will require massive amounts of energy. That translates directly to "money". There will always be money unless someone finds a way to negate the second law of thermodynamics.
The dependency tree for anything in the software world is so large, that liability like you describe is not feasible. Tomorrow Anthropic's latest model will find a RCE in SYNs being sent to a server? Who is "liable" when you lose your Google account, your bank account, access to your car and all ways to prove to the government you are who you are all at the same time?
Others have already replied this is not exactly the case and it's trafficking weed and other drugs that gets you hanged.
That being said, I'm not so chill about weed. Weed people, like smokers before them, don't consider weed to be a big problem for the people around them and ignore anything you might have against it. That means you'll be laughed at when you ask neighbors to stop smoking two floors below you, to stop growing the plants in their tub, etc. It also means you'll have to go through a lot of places that smell like shit because people smoke weed there often.
Statistically, I would look at deaths from that age group among space flight science and compare this "blip" to the p50. I don't think it's easy to say if 11 deaths/disappearances over 4 years is high or not, without looking at the problem this way.
I'm so happy that EU and UK have laws against this kind of thing and so I will still be able to work somewhere in the future(TBD what future means, though).
Local AI is almost impossible right now with the prices of RAM and GPUs and the sizes of decent models. No way spending even an optimistic 10k, but more likely 20k, on a setup that is good for 5-6 months makes any financial sense.
I disagree wholeheartedly. Older models do not perform anywhere near as well as newer models, and certainly not once you throw in agents that can sense check, security check, refa tor and balance, and research queries as they run behind the scenes.
Impossible to find Mac minis in some areas, and if this goes through expect it to get worse.
I settled for the AMD rough equivalent. It’s not perfect but it can still handle most of the work. Now if only extra ram would come down in price… I find I need about 5 GB more than I have
While everything said here is true, I find that in JavaScript world depending on a package that was last changed 8 years ago, complete as it may be, is asking for trouble. For your case, I couldn't find the link to the package the account was changing, so I can't tell how big of a risk keeping the previous dependency is.
JavaScript ecosystems often end up with small, feature-complete dependencies where "if it ain't broke, don't fix it" is a reasonable stance, so staleness alone isn't necessarily a risk.
reply