I very much understand wanting to have a say against our data being freely harvested for AI training. But this article’s call for a general opt-out of interacting with AI seems a bit regressive. Many aspects of this and other discussions about the “AI revolution” remind me about the Mitchell and Web skit on the start of the bronze age: https://youtu.be/nyu4u3VZYaQ
John Oliver had a segment on this that may help convince people that it is real: https://youtu.be/3kEpZWGgJks
These two are not interchangeable or really even comparable though?
For GNU Make, yes they are. These are fully comparable tools for writing sophisticated dynamic build systems. “Plain make”, not so much.
[cmake] makes your build system much, much more robust, far easier to maintain, much more likely to work on other systems than your own, and far easier to integrate with other dependent projects.
This is absolutely incorrect. I assume (although I have never witnessed it) that a true master of cmake could use it to create a robust, maintainable, transferable build system. Very much like there are people who are able to make delicate ice sculptures using a chainsaw. But in no way does these properties follow from the choice of cmake as a build system (as insinuated in your post), rather, the word we are looking for here is: despite using cmake.
I apologize for my inflammatory language. I may just have a bit of PTSD from having to build a lot of other people’s software through multiple layers of meta build systems. And cmake comes back, time and time again, as introducing loads of obstacles.
Thanks for giving the link and making this an easy 1-click thing. Just donated.
ADA should be the lawful good.
Bash is chaotic neutral.
Java is lawful neutral.
Javascript fits ok as chaotic evil.
Move ASM to neutral evil.
And maybe f77 as lawful evil.
SAAB Gripen: Am I a joke to you?
After having a lot of sysvinit experience, the transition to setting up my own systemd services has been brutal. What finally clicked for me was that I had this habit of building mini-services based on shellscripts; and systemd goes out of its way to deliberately break those: it wants a single stable process to monitor; and if it sniffs out that you are doing some sketchy things that forks in ways it disapproves of, it is going to shut the whole thing down.