Comments

This profile is from a federated server and may be incomplete. Browse more on the original instance.

bitcrafter, to linux in Wine 9.0 is now available

A truly fantastic update for our times!

bitcrafter, to asklemmy in Ancient wisdom often sounds like common sense now that it is commomly taught. What is some ancient wisdom that we no longer teach because it was wrong?

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.

bitcrafter, to asklemmy in what are your fun, low stakes new year resolutions?

The resolution preferred by God himself.

bitcrafter, to linux in Gentoo goes Binary (packages)

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

bitcrafter, to programmer_humor in The Holy Trinity of JavaScript

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.

bitcrafter, to programmer_humor in The Holy Trinity of JavaScript

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

bitcrafter, to programmer_humor in The Holy Trinity of JavaScript

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.

bitcrafter, to programmer_humor in The Holy Trinity of JavaScript

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?”

bitcrafter, (edited ) to linux in KDE's Nate Graham On X11 Being A Bad Platform & The Wayland Future

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.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • localhost
  • All magazines
  • Loading…
    Loading the web debug toolbar…
    Attempt #