Ubuntu because it requires the least amount of hack fixes to get working.

And snap has vastly simplified software installation.

That’s rather optimistic. I’m pretty sure it’s daily. Although, perhaps it’s only once a month that it gets upvoted

That’s what I was questioning. Why do do the work but then not make it accessible?

It’s a similar thought to this topic: https://lemmy.world/post/3179113

I’ll rephrase. Why require an editor? The most common viewers of SVG do not support layers

Why not export them rather than requiring people to install Inkscape just to view the files?

I wonder if they’re just testing the waters to see if the sentiment has changed at all. They’ll probably keep posting similar at regular intervals to verify that the backlash is subsiding.

It sounds like your issue is with capitalism rather than GitHub. The same logic is applicable to many corporations.

Has GitHub actually done anything negative? Your comments really just sound like fear mongering, I can’t see any actual issues.

What is the bloat you’re referring to? The UI is clean and simple. Navigating and searching code is intuitive. The issue tracker is basic but reliable. Releases are clear. GitHub Actions are complex but featureful and incredibly useful. GitHub Packages are basic but useful. GitHub Copilot is damn impressive.

We should think about starting a GoFundMe to get the author the mental health support they so clearly need

Angry old man angry

Damn, You weren’t kidding. the article would be comical if it weren’t so worrying for his mental state.

I’ve only read the headline and first paragraph but… I already think there’s this is flawed.

It’s treating the symptom rather than the problem. Really we need to be standardising how applications are configured. Standardise the command line arguments, add logical defaults. Pick a single configuration format and a centralised location where is defined.

This is one reason I favour docker compose for running apps. Everything is configured through a docker-compose.yml file.

You should consider who your audience is, are they all CLI experts familiar with the difference in syntax? That seems unlikely.

I’d always write documentation in a way that’s accessible to most users. The difference between $ and # syntax is highly esoteric.

sudo on the other hand is familiar to almost everyone. It’s one of the first things mentioned in beginners guides.

I wouldn’t even prefix your commands with $ as an experienced user is quite likely to include that when copying the command.

A lot of people are citing the arch wiki as a standard that uses # but isn’t the entire meme around arch that its a notably complex system?

Can’t you just select the text without the sudo prefix…?

Aren’t you enjoying everyone listing their favourite text editors and the fact they use ssh?

Damn. Even the website documenting their design is ugly as sin.

Out of interest why do you favour snap over flatpak?