5,840 karma · joined March 3, 2010
Even if the program is very large and linking everything takes many seconds, breaking up the program into dynamic libraries should get you sub-second compiles.
We are more likely to get a 10000-page micro-managing land use policy with a whole new agency that can never hope to be as efficient as a single flat tax and free market.
<a bg="red" text="white" dark="bg:red text:white">link</a>Sure, some of the daemons are different, like upstart instead of systemd. And out of the box it supports Android apps and doesn't allow shell access outside a container.
But I don't see what's fundamentally different.
Flatpak and NixOS are more complex because it's worth it. For example, they don't duplicate exact versions of dependencies on disk.
Recently I discovered https://directus.io/ which comes pretty close and it's open source.
https://news.ycombinator.com/item?id=39217310
If you mention you are hiring generalists and the location / comp are reasonable, you'll likely get some hits.
Then to test locally you just do "make check".
The problem comes if you start using pre-made actions instead of simple commands.
D could have been something but most people avoided it because of the commercial nature, i.e. not being Free software.
Based on a quick reading it seems they are assuming the average supply is 130% of the average load over the year.
External systems come with a cost, especially if it's more than a library.
For stuff unrelated to Qatar, they are pretty unbiased. But that changes when their owners actually have an interest in the matter.