It’s definitely for hardware reasons. They have been aggressively improving the vector math capabilities in their chips, but as anybody who has tried to run a local LLM will tell you, newer hardware works better and you’re always limited in what you can do.
Because you won't run your sorting algorithm that runs every frame on a CUDA kernel. CPU performance matters more than however many tflops of CUDA you have under hand as soon as you do silly things like "run an OS" and "use your PC for anything but shitting out tokens"
Understanding and deciding to rely upon are not the same. Complexity is one of the biggest challenges in real world software systems. Keeping a subsystem’s responsibilities simple can do a lot for a system’s reliability. Most teams have extremely mature systems for managing complexity in their code - tests, CICD etc. Sure you CAN build all those things for your database too, but it’s more work. Most teams I’ve worked on choose to minimize database migrations because it’s a lot of work to make that part of the system as robust against mistakes as code is. Choosing to ignore a feature in your database is often a very rational pragmatic choice aimed at keeping complexity under control.
You could. But then you’re also building from scratch HA failover, backups, replica management, monitoring, etc - cloud vendor managed RDBMS come with lots of niceties. All of which are possible to set yourself. But a hassle, and difficult to make bullet proof.
This original author is mentioned in the second sentence of the linked article, and then again in the third sentence, along with a link to the original story.
They clearly have an agenda, but also openly acknowledge that public surveillance is a two sided coin, balancing public safety and convenience with privacy. Some of the risks they identify are real, but others are unabashedly exaggerated.
Correct. All major OSes stopped broadcasting the preferred SSID list by 2017, with Android and Linux being the last. Apple stopped in 2014. Windows by 2009.
reply