My kiddo and I are having a fruit and vegetable challenge. Each month we’ll seek out a fruit or vegetable we’ve never tried and taste it. My BFF is trying to walk all the greenways in our county (that is county not country, low stakes! Attainabl!). How about you?
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.
To speed up working with slow hardware and for overall convenience, we’re now also offering binary packages for download and direct installation! For most architectures, this is limited to the core system and weekly updates - not so for amd64 and arm64 however. There we’ve got a stunning >20 GByte of packages on our mirrors,...
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?”
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.
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.
Well known KDE developer Nate Graham is out with a blog post today outlining his latest Wayland thoughts, how X11 is a bad platform, and the recent topic of “Wayland breaking everything” isn’t really accurate....
Wine 9.0 is now available (gitlab.winehq.org)
what are your fun, low stakes new year resolutions?
My kiddo and I are having a fruit and vegetable challenge. Each month we’ll seek out a fruit or vegetable we’ve never tried and taste it. My BFF is trying to walk all the greenways in our county (that is county not country, low stakes! Attainabl!). How about you?
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?
This question inspired by this post..
Gentoo goes Binary (packages) (www.gentoo.org)
To speed up working with slow hardware and for overall convenience, we’re now also offering binary packages for download and direct installation! For most architectures, this is limited to the core system and weekly updates - not so for amd64 and arm64 however. There we’ve got a stunning >20 GByte of packages on our mirrors,...
The Holy Trinity of JavaScript (programming.dev)
KDE's Nate Graham On X11 Being A Bad Platform & The Wayland Future (www.phoronix.com)
Well known KDE developer Nate Graham is out with a blog post today outlining his latest Wayland thoughts, how X11 is a bad platform, and the recent topic of “Wayland breaking everything” isn’t really accurate....