Quite well known now because Rust-haters like to point out how they're awkward to use in Rust.

I mean yeah I guess that's its primary purpose if you totally ignore the fundamental thing it's meant to be doing.

It's like saying the primary purpose of a seatbelt is to be easy to fasten and unfasten.

did you even read it?

Yes I read and understood it. :-D

I probably shouldn't reply since apparently you're still working on learning how to copy text...

ruby is bad because python/js good

Yes indeed, if you actually read his text, Ruby isn't bad because Python/JS are good. It's bad because it has failed to add static type checking. Python and JS are simply examples of languages that didn't fail in the same way.

matz is good but DHH is bad and so ruby is bad

That quote says absolutely nothing about Matz or DHH making Ruby bad.

ruby is bad because it’s old

No, the text says that Ruby persists despite its badness due to inertia and nostalgia.

How can you accuse me of not reading it when you're pasting literal quotes that contradict you? Insane.

Yeah based on my experience of lots of people using Linux in companies, you're pretty lucky.

But obviously it can both be true that most people have no issues and it's really unreliable. Like, I would guess 20% of people in my company have serious issues with Linux - random crashes and not going to sleep in bags. That's really bad! But still 80% of people have no issues, which is why you always see confused comments like yours on forums saying they don't have any problems.

Historically, hyphens and underscores were treated as equivalent in the names of keys appearing in the file

This is why I strongly prefer underscores; never use hyphens if you can avoid it. Eventually the names will end up as variables in a programming language where you have to use underscores, and now you've got some stupid and confusing translation system to deal with.

Another example of this is CSS names in Javascript. Rust also made this mistake unfortunately.

This [key name in setup.cfg] has been deprecated in 2021.

I knew Python didn't take backwards compatibility seriously after Python 3.12, but 4 years is a joke.

so the social media publicity was required to resolve this issue?

Certainly seems that way unfortunately.

Yeah even though it definitely has flaws (awful CLI, dumb diff/conflict algorithms) and half-arsed parts (submodules, LFS), it really is pretty great software.

Still, I'm hopeful for the next generation VCS's - Pijul, Sapling and Jujutsu.

I do also agree with Linus that immediately running to social media to drum up drama is not the correct solution to getting it fixed.

So what is the correct solution?

I don't think libuv is really that popular, nor is it that confusing.

But I do agree it's not a very good name. "Rye" is a much better name. Probably too late anyway.

Standard ring buffers or circular buffers are implemented as continuous vectors, with a read and write pointer.

Rust's VecDeque is a ring buffer: https://doc.rust-lang.org/std/collections/struct.VecDeque.html

They're not that simple because of packfiles. But yeah loose files are very simple. Also the documentation for packfiles is pretty bad. You end up reading other people's random notes and the Git source code. (I actually have written a Git client from scratch.)

Git is a graph of commits and you can't really display a graph in any way except visually. Even the CLI has a way of showing it visually (git log --graph).

Think about other graphs you might interact with, e.g. node graphs in 3D graphics of music production. How many of them do you manipulate with a CLI?