My point about Cloudflare was more about them taking down essential services that could run just as well on-premises like a heating controller.
697 karma · joined March 12, 2009
My point about Cloudflare was more about them taking down essential services that could run just as well on-premises like a heating controller.
If you design your system according to the guidelines you usually end up with a product where it's easier to service your customer (eg. with full account exports). Deleting inactive accounts is great because it means less migration headaches in the future.
This is also why our privacy statement starts with "We […] don’t really want your personal data."
Besides, the specific extension we're talking about protect registers and computation and not shared memory.
Consumers are finding out the issue with cloud computing when their heating system can't turn on because Cloudflare is down. A cheaper and more reliable solution is still on-premises computing.
Large social network and content platforms don't have any incentive to keep your data safe because they want to monitor and own everything.
Maybe this is for something like a government running a public service?
In other hardware there is an OEM secret because the manufacturer is trying to keep users out of "their hardware", in this case we're trying to keep everyone except the data owner out.
One, it makes it appear that all ethical and social conventions for the one can be applied to the other and it's a done deal.
Two, it makes it appear that conclusions are also reversible, and that turns seemingly enlightened libertarian ideas into munition for racism.
There is a way to discuss if keeping intelligent artificial life under servitude without using those terms, especially if you're on a new account.
> as a stopgap until they get further with renovation work
I assume they know what they are getting into.
Eloy designed CocoaPods to be the absolute minimum we needed to deal with dependencies for the projects we were working on. So that meant:
* Rely on GitHub for hosting so nobody would get bankrupted running the repo, with the option to switch over to self-hosted in case that ever became necessary. * Use Git and existing project tools on GitHub to deal with external contributions for pods. * Use Ruby for scripting because that was what people used most at that time. * Use Ruby for pod definitions for flexibility and reduced development time (ie. so CocoaPods didn't need a parser).
For a long time this was a one-person effort.
All of those decision obviously have downsides, even more obvious now you have to power of hindsight given years of incremental improvements on speed and security of dependency managers.
I think Eloy did a great job in general and the popularity gained speaks for itself.
You can look for things like "nvidia drm broken" and find thousands of threads of people all types of problems spanning decades, meaning; old and new. Some of them are pure driver issues caused by NVIDIA but that doesn't matter because we're not trying to assign blame, but we're trying to see if the ecosystem is "mature".
It does not use any of the popular desktop environments (unless you drop into Desktop Mode). It heavily curates hardware, kernel, and drivers to keep the platform from breaking and install with sane (performance) defaults for gaming. It doesn't rely on a common package manager.
Beside a Steam Deck I also use a Linux PC for gaming and even with 25 years of Linux experience I still struggle sometimes to keep hardware acceleration working after a driver update, sometimes spending an evening of troubleshooting instead of gaming. Certain parts of the desktop environment sometimes lock up to the point where I have to SSH into the PC to fix it. It's like owning a vintage car in a certain way.
And yes, I prefer all of that over the Windows experience, but it's not seamless and not simple enough for anyone to just jump into.