Python packaging and stability is a total mess. It has gotten to the point where I just look for alternative tools when I find out something new I found is written in Python.

the info required was there already, just you needed to put effort in

Not really. This is mostly what this is all about. The companies are insisting that open source projects should do analysis of security impacts in addition to fixing the bugs whenever some “security researcher” runs some low effort fuzzing or static analysis thing that produces large numbers of bug reports and assigns CVEs to them without the consent of the project. The problem is that such an impact analysis is significant effort (often orders of magnitude more than the fix itself) by people with deep knowledge about the code bases and only really useful to the customers of those companies who want to selectively update instead of just applying all the latest fixes.

While true essentially forking the latest stable version of the kernel to make an LTS branch or a vendor version only multiplies the problem, it also does not contribute to solving it.

The worst thing is when it happens in this way and you can’t remember even though it was your own question https://xkcd.com/979/

Yeah, but when was the last time you decided to upload hardware device data for a root server to some hardware survey? That is something almost exclusively done by the kind of people who want to show off their system in some way.

I wonder how representative that is of actual software used. I would imagine hardware probes are run from installers and live systems quite frequently. I would certainly not expect several percentage points of “neither” in practical settings.

that even the thousands of developers who wrote most of that code don’t understand how their own code works anymore?

The bugs I have fixed that were written by that idiot “me from a few weeks/months/years ago”…

Any of those 2,034 people can push malware to Fedora

Maybe, but that is still a significantly higher bar than allowing everyone to publish a package the way most language specific package repositories work (or just use any random github repo even like some others).

“you’re using it wrong” seems more like the official motto of Wayland whenever anything that isn’t working on it is brought up.

There are so many people who think sid is a distro when really, as far as the Debian project is concerned, it is a staging ground.

The ability to set static routes via DHCP server or for that matter the ability to remote boot systems via DHCP server which has similar problems if you can’t trust the DHCP server.

I would go so far as to say that languages that allow you to leave off the braces and have macros that look like functions that can generate multiple statements at the same time are just plain badly designed.

Also to advocate for a specific tab size while also advocating for hard tabs is nonsense. The one flimsy claim to usefulness tabs have is that different people can use different tab sizes and all at the low, low cost of everyone having five times more work to use tabs for indentations and spaces for alignment and thus having to use visual whitespace of some kind.

Agreed, anything below 5 FPS is probably a bit slow for a text editor.

So it doesn’t run at a wastefully high FPS for a text editor? Is that supposed to be a selling point for Zed that it renders many, many more frames than a text editor needs?

It does matter if people now advocate to routinely disable useful features by default because they are a problem for their particular use case.

That “vulnerability” seems more like a case of “people who use hostile networks have not considered which features that work as designed should be disabled in their use case”.

Not sure about the down arrow in particular but I have seen objects (e.g. a corner of a book) accidentally lie on a key at the edge of a keyboard before.

The public key contains a user name/email address string

No it does not. That is just a comment field.

Every single command, option and argument in the shell is split by spaces, regardless of what it contains. That is clearly the more common case. I am not talking about splitting when the space comes out of a variable but in general, as part of the syntax.

I am well aware of how quoting works to avoid accidental splitting and it is an absolute non-issue in practice once you get used to quoting things, about as annoying as the fact that you have to quote strings in every other programming language, i.e. not at all.