backgroundcow

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.

It is fully possible, quite likely even, for models to both be "more accurate than humans" on average while at the same time suffer occasional "accuracy collapses".

Actually

Crush both apples with the blunt side of the knife. Divide applesauce equally.

"Absolutely, rest up" is more than sufficient in 99percent of cases

Internal monologue: "But wait, will it come off as impolite if my reply is this short? I better add something about how I'm sad to hear that they are sick. And maybe also something that I hope they will get better soon. Hmm... how do I say that without sounding like I expect them to be better soon-- that they can and should feel allowed to recover at their own pace? But, now it sounds as we don't need them at work-- I also want them to feel missed. Also, is there a risk they take 'rest up' wrong?, as if it is their fault they are sick because they haven't rested enough?-- I'd better soften up that formulation. Then, how do I start this email? 'Dear x,' seems too formal, maybe 'Hey,' -- no, that sounds like 'Hey listen up!'; maybe I'll just skip the greeting to make it feel more like a casual conversation. Do I still sign the email? With "Regards?", "Best regards?", "Sincerely?", "With wishes of swift recovery?" Should I also cut the email footer to make it seem less formal? What if they need to forward this to show that they have my permission? In that case the formal footer is probably useful.... etc. etc.

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

What you describe is more or less the Nordic economic model, except the basic income. Corporate abuse is low, because it is not unthinkable to "not work" in response to such abuse, but also because unions are strong. Nevertheless, a lot of people still work a lot, so it doesn't completely change the work/life balance oddity op is posting about.

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.

Cmake

Thanks for giving the link and making this an easy 1-click thing. Just donated.

On the topic of things to never forgive Redhat about, aren't there other things that are more pressing? Like, inventing a whole scheme to circumvent the idea of the GPL license via service contract blackmail?