For lots of software projects, a release tarball is not just a gzipped repo checked out at a specific commit. So this would only work for some packages.
It's not fine, it's precisely the kind of thing that needs to be regulated because the average consumer is not capable of understanding the non-obvious long term consequences.
> the Rust community putting a lot of effort into making memory safety a priority for everyone in the industry
It would help if they did that in a manner that resembled harrassment a bit less. I realize most of the community means well but by now it should really be clear that they picked the wrong way.
C knowledge is still way more generally useful than javascript and/or web knowledge. Whatever you think of C there's no denying it's everywhere and understanding it is relevant in pretty much every software system in existence, even when that's not immediately obvious.
The problem with this analogy is that nobody knows that Gnome != wayland. Not even gnome developers know gnome != wayland. As a result, a lot of people hate wayland because of gnome's failed switch to wayland. And a lot of people hate gnome for their pretentiousness.
Perhaps they should be disappointed in nvidia? Or at least, think twice before buying from them? I don't think anyone here demands anything from nvidia. It's not wayland devs that feel entitled to better treatment by nvidia. It's nvidia users feeling entitled to support in wayland compositors.
> No, but Wayland is not a bit of software you even think about until it goes wrong. That means the internet gets disproportionately filled with posts about Wayland not working, which presents the wrong image.
Kind of like reverse survivorship bias. The only wayland sessions that get attention on the internet arw the ones that don't work.
The 'wayland sucks' movement is sooo annoying, even to me and I'm just a happy wayland user and haven't spent any of my free time writing those thousands of lines of code.