You always do some testing in production. You can do unit testing, integration testing, and even some load testing before deployment, but you will always find bugs once it’s rolled out to production with a bunch of variables you cannot control and couldn’t have possibly accounted for. That’s why most software has point releases, it’s inevitable on any marginally complex software.

I thought maybe Minecraft would run faster on it. It didn’t, but it kicked off a learning process.

It’s rather bold of many of the commenters in this thread to assume they know the needs of Mozilla and their developers rather than those people themselves. GitHub makes complete sense, even if it doesn’t live up to some people’s desires for free software purity.

Group voice is discord’s biggest feature, but also general messaging (both direct/group as well as communities), video streaming, and file sharing.

Element might be a viable alternative, I’ve used it for chat where it certainly is, I haven’t used voice but I’ve heard some people say that video has a very high delay. My friends and I will often share screens for one reason or another and I’m not sure that the experience would be comparable in Element yet.

Mumble isn’t comparable because it doesn’t implement any of the same features other than voice, it doesn’t have persistant logins, etc.

I mean it already is, Linux gamers play with their windows/mac friends. The alternatives aren’t as easy to use.

ruff

I discovered ruff earlier this year as the project was really taking off. It’s a python linter, and very recently now a formatter too. Its main selling points are that it is insanely fast and implements features previously provided by dozens of different tools. It was a pretty easy sell at work due to its speed, and the guy who initially wrote it now has a startup and they seem intent on expanding to cover more tool categories. It’s been a huge improvement for my work as a python dev.

Protocols are static duck typing. An object is a valid instance of protocol if it implements all the methods defined in the protocol, even if it doesn't declare it as implementing it. That last bit is important and the most distinguishing factor compared to an ABC.

I wish it were irrelevant. It's the default in a lot of non-hobby use cases. Even if it's nobody's favorite, switching requires a business reason and certain degree of consensus among devs/managers/partners/customers.

It's super confusing, like I feel many commenters there live in a different universe. They talk about how Wayland is a failure that has failed to get off the ground, while it's the default in most of the major distros at this point.

The phoronix forums are insanely toxic. Everything is bad. Gnome = kid's toy. systemd = written by Satan himself. Every programming language = too slow. Anything vaguely interested in fostering a diversity, equity, and inclusion = true colors come out in full force.

It's so toxic yet I subject myself to it every now and again. There's absolutely no moderation going on and it shows.

Systemd is the first program that runs once the kernel has started. It's job is mostly just starting up other processes, and managing those other processes. If you don't know what systemd is, then you probably shouldn't care about if you're using it or not, it's good software but there are fine alternatives.

What makes systemd particularly interesting is that it is different from historical init systems. Historically these init systems were an unholy mess of shell scripts. This offers maximum flexibility, but limits the functionality of the init system itself. Systemd replaces these shell scripts with simple ini-like service files that allow everything to be declared simply and declaratively, and allows specifying more rich metadata, like dependencies. But it's different, and some people place a higher value on "how it's always been" than pragmatism. I personally have zero sympathy for them because throwing out objective progress to hold onto a broken system designed for 1960s computing is just dumb.

Endeavor seems like a better option. The majaro devs don't seem particularly trustworthy as OS devs, mainly because they hold back security updates as a policy and have allowed things like ssl certs to lapse multiple times. Endeavor gets you the benefits Manjaro provides without the nonsense.

This is my fault, I did that. The honest answer: it was really easy to implement and now the app does by default what I prefer, I hide the comment action bar of course. In the future I want to add options to control gestures on comments, just haven't gotten around to it yet.