bitcrafter @ bitcrafter @programming.dev

Posts

2

Comments

282

Joined

2 yr. ago

That approach makes a lot of sense for amateur web sites, but less sense for professional web sites.

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?

In fairness, the actual title of the article is "What's Your Go-To Java Stack [emphasis mine]".

Thanks, it's actually kind of nice to hear someone who likes using PHP explaining in detail why they like it.

The founding fathers did not believe in universal suffrage; at the time only people who owned land could vote--to say nothing of even less privileged groups than that--and they were fine with that policy, in part because these were considered to be the people with the most skin in the game.

The resolution preferred by God himself.

Wow, when I went to bed yesterday it was only December 28, but now it is somehow already April 1!

The explanation given to you makes it sound like == was deliberately designed to be a more convenient version of ===, but what actually happened was that == used to be the only equality operator in JavaScript, which meant that if you didn't want it's auto-coercing behavior then you needed to go out of your way to add additional type checks yourself. Because this was obviously a tremendously inconvenient state of affairs, the === operator was introduced later so that you could test for equality without having to worry about JavaScript doing something clever underneath the hood that you weren't expecting.

Sure, but it is also a very gratuitous and pointless design constraint.

Land mines are painted red in my shop. You want to change the language to remove a land mine that everyone competent already knows enough to step around. The problem has already been solved, so why are you continuing to complain about it?

Just to be clear, I'm not actually calling for JavaScript to change, I'm just pointing out that people are right to point out this as being a problem. Having said that, if everyone competent uses linters now so that this feature isn't used in practice anymore, then getting rid of it shouldn't even break anything, and arguably code which would break is already broken because it uses an operator that no one should be using, so you shouldn't be using this code anyway.

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.

Yeah but performance has way more to do with architecture than it does code readability.

Indeed, I am a bit notorious at work for speeding C++ code up by rewriting it in Python, and I have been able to do this not because my Python code is particularly fast but because the architecture of the C++ code was such a complicated and inefficient mess that it actually managed to be slower than Python.

Thank you for taking your time to make sure 0.19 is stable before upgrading! I recently switched here from another instance because they upgraded while 0.19 was unstable and it broke a lot of things.

No, if anything the way you can tell you are in a dream is because the top spins forever and never starts wobbling; the way he got his wife to eventually concede that she was in a dream was by setting the top in a perpetual spin so that she stumbled upon it still spinning.

The significance of the ending is not that he is still in a dream but that he is so content with the situation that he stops caring whether he is in a dream or not. (Actually, in fairness that is not quite true either; I've heard that basically the ending is more Nolan trolling the audience than anything of narrative significance.)

Yeah, which is why I thought that the original ending to Return of the Jedi, which was just a local party with the Ewoks, was much better than the immediate galaxy wide celebration that Lucas insisted on adding in the re-release.

With most series of this length, towards the end I've tended to wish that the author would just wrap things up already so I could find out the ending and move on with my life.

With this series I actually got sad as I made my way through the last book because it meant that the story was going to end soon and I had been enjoying it so much that I didn't want it to end. (Having said that, I also absolutely loved the ending, which is also unusual for me for a series that is this long!)

In fairness, sometimes it is useful to get hands on experience with a system before you dig into its fundamentals so that you have a reference point that helps you absorb the information.

I think that much of the disparity is explained by the fact that the Apple case was decided by a judge but the Google case was decided by a jury, so the people making the decisions had very different perspectives.

Also, because the decisions were so different despite the similarities between them, Google probably actually has a pretty good case it can make in the appeals process, so I wouldn't consider this outcome to be the final word just yet.

Q: Why the name "Fleece"?

A: It's a reference to the mythical Golden Fleece, the treasure sought by Jason [emphasis mine] and the Argonauts.

I see what you did there...