There will always be a controversy, we just don’t see each of it. The recent one you talk is probably about the talk a Rust developer was giving and where the toxic C dev didn’t let him speak. Or is there a more bigger and recent controversy? Nothing happened to it, it happened, people discussed it and now its history. Development continues and its in a good position as it seems.

Tik Tok doesn’t become better just because another one creates the same.

deleted by creator

That’s a lot. But that also means your system is not very secure, as you are missing ton of security patches for the packages.

34 days without booting? Are you using a Debian system and don’t update often? You should, for security patches at least. I’m on an Arch based system and update every day. Sometimes there are updates that require a reboot, so all services are up to date. My system is often up for a few days, sometimes even for a week.

Small tip, logging out and in will have a semi clean environment without a full boot. That means the uptime won’t reset.

And the Garbage Collector in Go is also a thing that helps ton for most normal work. To be honest, I wish sometimes Rust had an optional GC mode (I know this would be against the principles of the language… don’t take this wish too seriously). I see it like C with a GC+Concurrency. And one should not forget, because the language is dead simple, the compiler compiles extremely fast; even suitable as an interpreter language basically (purely judging by speed metrics).

But after being exposed to Rust, I do not have fun with Go because it misses some really cool or basic functionality; like proper error handling. Ultimately these are different approaches and that’s good. In example functional programming works a bit differently and we are not saying they should give up on this approach, because you like C so much.

I’m in a similar position. I tried Go too, but its not a fun language to work with for me. But I get what they are aiming for, a very simplistic language without too many features or structures, inspired by C itself. In fact one of the Go language developers is Ken Thompson, who developed C language itself too.

And you know what, that’s fine. Not every language has to offer everything. There are huge portion of people who like this approach. You can easily begin programming in Go, after a few hours or days of learning. There is really not much from language perspective to learn. I don’t have to like it, but others do, and that’s fine.

If anything, I would look at Zig instead Go. Zig is also not very complicated. Its even closer to C and can run C code directly. Its kinda the child of C and Rust.

Agreed. This term “unixporn” bugs me. I cannot recommend those platforms to anyone, because of the direct use of “porn” term. Its like kiddies made up the term unixporn or something…

Removed by mod

Hopefully political stuff like this will not hurt the game.

deleted by creator

deleted by creator

deleted by creator

TL;DR: My desktop PC uses EndeavourOS and the only immutable experience I have is SteamOS 3. I can’t say one approach is better than the other, but I like having the newest software and packages in my system. And that’s best provided with a rolling release. I also think that sandbox systems like Flatpak and the several alternative installation methods besides the system package manager is an added complexity for a new user in Linux.

I don’t mind using an immutable system (BTW another term that describes this kind of system is Atomic, which comes from Fedora), as long as it is designed around it and works well. The only immutable system I use is on my Steam Deck with the pre-installed SteamOS 3. My generic desktop personal computer is using an Archlinux derivative EndeavourOS with a rolling-release, where I have much greater control over the system.

Both systems have their strengths. I don’t think that my mutable and always up to date system is breaking more often than the other system. The best part of it is, its always up to date and I get the newest applications. I try to not use much Flatpaks or AppImages (but do for certain apps, where I have no other choice for ease of use). And an immutable system naturally basically asks me to use Flatpaks and other user space package formats that is not handled by the distribution itself.

Even though I have some thoughts on it, I am not excluding one approach. Many say that immutable distributions are good for new users to Linux. I think this adds some complexity and problems, because they need to use sandbox systems like Flatpak. And that’s if they know that they are using Flatpak, because sometimes the app distribution gives options like AppImage and custom installer scripts as well. This is all confusing for someone who just starts with Linux. On top of it, the sandbox of Flatpak requires some additional setup and configuration for some apps, to access certain hardware or filesystems in example.

All in all, I tend to like the traditional “mutable” distribution system as a rolling release model the most. But I’m an not excluding any other and would use a good “immutable” one; I just didn’t try any other than the one in my Steam Deck.

Serious question: I see the topic about Discord screen sharing a lot. Why is this such a big deal?

Deactivating Wordpress contributor accounts does not prevent any forks. I don’t get what the benefit is to ban them. Is it just to demonstrate his power?

In many countries in the world it makes a huge difference to not having a license. If its not properly licensed or licensed at all, then it means in many countries in the world the most restrictive one, the entire opposite of the goal: Do not use without permission. By not putting the license text and clearing things up for the user, means it is not properly licensed. Therefore in countries like Germany this project would be a violation to use without permission. It becomes a liability, as the person could potentially sue anyone (in those countries).

I don’t think its enough to link. You just need to copy or create a single txt file named “LICENSE” and put it in the root of your repository. I am not a lawyer. The license text will tell anyone who cares to know what they can do and cannot with the project. If you do not do that, you only make it harder for anyone looking for the license (as explained with the websearch example previously).

I think you need to put the actual license text in the repository, to have a license. Just stating a license name in the readme is not correctly licensed. In example people need to a websearch for this accronym in order to find their rights and who knows if they find the correct license. Maybe they find a different written one by another person. In example there are two “official” versions of this license: https://en.wikipedia.org/wiki/WTFPL

Wish I had.