renaming symbols, presenting documentation, formatting files,

Yes, these are supported via the Language Server Protocol (LSP). I’ve mostly been using it with the Rust LSP server (rust-analyzer) and well, it typically works, but sometimes you have to tell it to restart the LSP server and stuff (which isn’t a huge ordeal, but don’t expect everything to always work as well as in a full-fledged IDE).
I believe, for formatting, there’s also some non-LSP support.

showing code diagnostics beyond syntax errors (for example code smells or so),

This is supported in principle via LSP, too, but it depends on the specific LSP server, how much info it provides. The Rust compiler gives out relatively much on its own, which is passed on by the LSP server, but you can apparently also configure it to use the linter on save.

have AI integration (explain this, rewrite this, replace this with prompt output, …),

Not out of the box. There’s a way to define “External Tools”, which basically allows you to run commands and pass arguments to them and then use their output. For example, you should be able to define an External Tool, where you can select some text, then press your keyboard shortcut for that tool, so it sends the selected text to that tool and then it takes the command output and inserts it instead of the selected text.
While this is a powerful concept, I don’t know, if you hit limitations at some point.

specific framework integrations (reactjs, django, actix, …),

Nope, except where this might be covered by LSP. But there’s no obvious way to just install additional plugins, for example. You get about thirty built-in plugins and that’s it.

and stuff like expanding macros in C/C++ and Rust?

Well, expanding macros is also possible with the Rust LSP server. Don’t know about other languages.

Mindustry is basically Factorio with more focus on tower defense.

openSUSE has the best integration of KDE, but I wouldn’t expect to see issues like yours on any distro, really…

Also kind of breaks immersion when there’s tons of different enemies, but they never fight between themselves. Only when the player character shows up, they’re like, imma ruin this woman’s life.

Yeah, good point. It also doesn’t update when the content of a file changes. So, in order to detect a change in a directory, you have to walk all the files and sub-directories and the directory itself to get the last-modified timestamp for each of them. Then determine the highest last-modified and compare it to what you measured in a previous run. If they differ, a change happened.

Yeah, I’m building more-or-less an alternative to make. Major difference is that I’m not using shell commands, but rather users will define their build code in Rust …because it’s intended to be a build tool for Rust applications (beyond what cargo does).

Thanks for the comment, though. So far, I haven’t limited inputs to just be files, so I don’t actually assume to have a last-modified timestamp. Rather, my assumption is that I can get some value which changes when the input changes. In the case of a file, that’s the last-modified timestamp, but theoretically, it could also be a hash. But that means I have to store these values to be able to detect a change. Being able to just say that one thing is newer than the other without storing anything, that is pretty cool and might be worth changing my assumption for.

I don’t think, inotify works for me, because I don’t have a continuously running process. My users rather just run some build command and then I go and check, if any input files changed since the last run.

Frankly, I would be surprised, if anything uses groff for displaying --help, unless it shows the man page for that.
The most basic implementation of --help is a manually formatted multi-line string written into the source code, which gets printed as-is.
For dynamic layouting, you do need more logic, but rendering it to groff source code first does not make that easier. For tabbing, you print an appropriate number of \t.

openSUSE, because of the snapshotting. It’s zero-setup and just gives peace of mind when doing upgrades, as I can roll back even from the bootloader.

I have no experience with this, but I figured a Rust library might have tried to solve it (static linking is very much the norm here) and I found that ash can statically link the “Vulkan loader”. I don’t know, what that actually means, for example whether it would still load libxcb at runtime. Might be worth looking into what they do…

See the “Optional linking” section here for their description: https://crates.io/crates/ash#optional-linking

Needlessly absolute take. Yes, there’s going to be parents, who’d rather pay extra than look into what other games they could give their kid, as well as loyal Mario fans, who will pay pretty much any price. But there’s obviously also players who do weigh up their options based on price, and who will make different decisions when they have to decide between two titles, when one of them is cheaper. Especially with the additional invest for a new console and the more dire economic situation, I could see many players not buying into the Switch 2 at all.

I mean, if it’s still shit and it’s getting even worse, I don’t know why we wouldn’t continue to mourn that, or at least call it out.

Well, as the other person said, it was not a failing of LiMux. It was political. Munich had been ruled by one coalition throughout the lifetime of LiMux and after it went to a different coalition, they announced the switch back.
The manager of Munich’s IT department also publicly stated that they were surprised by the decision, because there are no larger technical problems and compatibility is resolved by providing virtualized MS Office, where necessary.
Coincidentally, Microsoft also moved its German headquarters from just outside of Munich’s tax region into Munich around the same time.

Well, traditionally, console prices were subsidized by the more expensive game prices. They’d sell the console at a loss to then make that back per game. Them raising both the console price as well as game prices is what makes it awful.

Good way to extort get Microsoft to offer competitive prices. ¯\_(ツ)_/¯

But yeah, it was the city of Munich that had a few goes at this. Now it’s the state of Schleswig-Holstein.

Yeah, I don’t have first-hand experience with Arch for that reason either. Well, and also because I do want a distro to set things up for me. You could set up the snapshotting (with BTRFS and Snapper) on theoretically any distro, but not having to figure out how and what settings are good, that’s why I go with openSUSE.
I might look into NixOS at some point. It obsoletes the need for OS snapshots, because the entire OS configuration is made in configuration files. But from what I hear, it helps to be a programmer (which I am) to really appreciate NixOS.

And yeah, don’t know much about Bazzite either, but from what I’ve heard, it really has some design decisions that make it feel more like a games console. The atomic/transactional updates, for example. As I understand, updates and such are applied to a copy of your OS, which gets swapped in when you do the next reboot. This helps keep the system stable after applying updates, but implies that you can’t really just poke around manually in your root partition.
It can be helpful for users not looking to experiment, but yeah, can be a pain, if you do want to.

As for a real-time kernel, the JACK FAQ says you don’t need it, but the distro might limit real-time scheduling anyways: https://jackaudio.org/faq/linux_rt_config.html
I’ve had JACK running on my system about a year ago, although I didn’t really have a need for low latency, so I can’t say, if it actually worked correctly.
Perhaps also worth pointing out that “Pipewire” is becoming a thing, which tries to make interfacing with JACK and PulseAudio much easier. I believe, I also used Pipewire back then. But yeah, folks who’ve dealt with JACK a lot more than I have, seem to be really excited about it, so it’s presumably doing a great job.

Yeah, I always hesitate to recommend distros. 😅
There’s tons out there and they all exist, because some smart person decided to put in lots of work, as the existing ones didn’t match what they wanted.

If we exclude Ubuntu/Debian-based, that narrows it down somewhat. The other major distros are:

• Fedora: Rather much tied to the corporate side (Red Hat / IBM), tends to be rather up-to-date. Kind of has a focus on GNOME, but other “Spins” are available.
• Arch: Community-driven, pretty much a DIY distro, so the initial setup is somewhat challenging. It’s really up-to-date, so much that it’s referred to as “bleeding edge” (rather than cutting edge), meaning you might get faulty updates from time to time. It’s also often loved by minimalists, because they can decide for each component, if they want to install it.
• Well, and perhaps the most niche of these – which is what I’m on – openSUSE: Has the best integration of KDE (not by a huge margin, but still). I like it in particular, because of its snapshotting system. It automatically starts snapshotting your OS (not the user files) once per hour or whenever you make changes to the installed packages. If something breaks, you can boot into a previous snapshot from the bootloader and roll things back.
  It’s the most “maximalist” mainstream distro, in that it preinstalls relatively much software. Personally, I think the other distros are a bit silly with their minimalist tendencies, but yeah, I’m biased. And well, downsides of openSUSE are that it is somewhat niche. You’ll find a helpful, tight-knit community, but it’s less likely that guides mention how to do things on openSUSE. Similarly, you’re less likely to find pre-packaged software for openSUSE. May have to compile from source more often, although SoS has a good amount of software, too.

As for whether a different distro is too much experimenting, if you do jump into it, you’ll understand why I talked about the desktop environment instead. 🙃
The DE makes a much bigger difference. Some people conflate distro and DE, because certain distros will have certain default DEs.
But if you used the same DE on two distros, honestly the main difference you’d notice is a different package manager. Where Ubuntu Studio and Mint use apt, openSUSE uses zypper, Fedora uses dnf and Arch uses pacman. They handle somewhat differently, but largely do the same things (i.e. install/update/remove packages).
Obviously, there are more differences to the distros, like how quickly they update and some of the default configuration, like the snapshotting I raved about, but ultimately it’s still a Linux system with much of the same software running on both…

Well, that was kind of a general statement. Mint is boring. That’s what it’s good at. That’s why it’s loved and why it’s recommended for new users. Specifically, it’s similar to Windows in many ways. It’s somewhat more customizable, but that’s about it.

With you having used Linux twice before, you could consider something less Windows-like, less boring. I’ll be talking about the desktop environment (DE) rather than distro, because it has much more influence on this. You can use these DEs on various distros.

• My personal favorite DE is KDE Plasma. The default-layout is also Windows-like, but it’s got all of the bells and whistles and options you could imagine. It’s kind of power-user heaven and almost like a toolbox to build whatever workflow you want.
• The other big, popular DE is GNOME. It’s more macOS- and Android-like and focuses on a specific workflow. People who can get used to that workflow, then often really like it. The workflow itself is sometimes frustratingly uncustomizable, but it’s also fairly customizable when it comes to the details, typically by virtue of also having lots of features, which can then be customized.
• Well, and I guess, I’ll throw in Xfce, too, since that’s likely what you used, back when you used Ubuntu Studio. (Ubuntu Studio uses KDE since the October 2020 release, but used Xfce before then.)
  Xfce isn’t necessarily what modern beauty standards would get flustered by, but many folks like it for its simplicity and because it is perhaps even more boring than Mint (without being Windows-like). There’s a good chance that it still works a lot like back when you used it.

Perhaps also worth mentioning that Mint’s DE is called “Cinnamon”, although it’s developed by the Mint devs, so if you like that a lot, it’s typically worth sticking to Mint.

I mean, yes, but I was rather wondering, if that extra space was maybe why it couldn’t find it. Maybe you had to manually enter the SSID and accidentally put in that extra space? Then again, I don’t even know, if you took that photo…

'fucking shit router ’

🤔