Choosing to have a child later on generally has fewer negative consequences than unchoosing a child you have already had.

Have you really not heard of it? It is a new architecture that is a bit better than x64_64.

Sure, but if you are not regularly expressing code that has the potential of summoning elder gods that will swallow your soul into a dimension of ceaseless screaming then are you really living?

I find the author’s writing style immature, sensationalist, and tiresome, but they raise a number of what appear to be solid points, some of which are highlighted above.

I tried reading the article and gave up because life is too short for me to read a tiresome article making points that aren't even particularly that new.

Huh; I don't believe that it is really him.

If this is the real Slim Shady, would you please stand up?

All of these options are still better than spending full price for a pair of jeans that were lovingly crafted to start with holes in them!

Either way, it’s an awesome language, happily been using it for decades now

Mind taking a moment to share why you like it? I am not very familiar with it.

I appreciate this sentiment a great deal in general, but sometimes it is difficult to uphold when I have to regularly deal with "time vampires" who not only require that I explain the same thing to them over and over again beyond reason but who also show no willingness or ability to actually learn the thing that I am explaining to them; at some point I just run out of patience and start ignoring them to the extent that I am able.

This news story is literally about the FTC actively suing for injunctive relief; the "complaint" in question is actually a formal legal letter addressed to the U.S. Ninth Circuit Court.

Edit: fixed typo

Wait... I just noticed this:

[XHTML] never took off on the web, in part because in a website context so much HTML is generated by templates and libraries that it’s all too easy to introduce a syntax error somewhere along the line; and unlike HTML, where a syntax error would still render something, the tiniest syntax error in XHTML means the whole thing gets thrown out by the browser and you get the Yellow Screen of Death.

This confuses me; don't you want to make sure you are always generating a syntactically valid document, rather than hoping that the browser will make something suitable up to work around your mistake?

That's a little bit like saying, "I don't understand why people continue to complain about the landmine sitting right there on the ground. We've painted it red so you can easily walk around it, so how has the problem not been solved?"

Alternatively, instead of reading a Phoronix article that has a couple of short snippets from a much longer blog post, you can read the original blog post yourself to see the full context.

Edit: Also, it is worth noting that the author of the original blog post had previously written another relatively recent post criticizing the way in which Wayland was developed, so it's not like they are refusing to see its problems.