Well… isn’t it? If one’s daily or most frequent back-and-forth journeys don’t exceed 100 ㎞, then a 160 ㎞ range is indeed fine.

Uhm… No. Most people only have one car so if you get one that only works 95% if the time it’s going to be super inconvenient when you have to hire a car every time you go on holiday or visit your family or go to a distant concert or whatever.

That’s why low range electric cars are not very popular.

Because most users simply use the browser

This is the same problem as saying “an electric car with 100 mile range is totally fine because most journeys are well under 100 miles”.

Most of the time I’m only using a browser (or VSCode). The annoying thing is the 1% of times when I want to print something, create a shortcut, use bluetooth headphones, configure a static IP, etc.

Use Photopea instead. It’s practically a copy-paste of Photoshop but in the browser, created by one person. Or if one has never used Photoshop before, try GIMP first.

Saying Photopea or GIMP is “practically a copy-paste of Photoshop” is laughable. Paint.NET, maybe.

No, I said that some important features don’t exist. They said “well I don’t use them”, as if that somehow negated the point that they don’t exist. It’s typical “works for me” nonsense. You get these replies whenever anyone says anything is suboptimal about Linux. It’s so tedious.

Good for you I guess?

These are probably the biggest reasons, but I think even after literally decades of development the actual desktop is still far behind Windows XP in many respects.

For example today I wanted to add a “start menu” shortcut to a program I had downloaded. The most popular answer is to *manually create a .desktop file and copy it to some obscure dot directory! Hilarious. Even Windows 3.1 had a built-in GUI for this.

Ok so there is a GUI to do it, but it isn’t actually integrated into desktops and isn’t installed by default. You have to install it separately.

It’s the same for things like WiFi settings! There are some settings in GNOME but most are hidden in the third party nm-connection-editor (from memory) and of course GNOME doesn’t have an “advanced settings” button to open that.

There are so many of these paper cuts I think Linux would be quite a frustrating experience for many people even if if had Windows-level hardware support.

I also can’t see this changing any time soon. Not that many Linux devs actually care about this sort of thing and many of them don’t even understand that it is a problem in the first place. Cue replies.

Sure… I mean why are you wary of them because they work with the US military?

due to their support of the US military

What?

I find the git CLI pretty intuitive

You might be the first person to ever say that! How do I delete a remote branch?

Still better than Device Tree though right?

that they would disclose on their website

Wouldn’t it make more sense then for them to simply host the Flatpak themselves? I kind of thought that was the whole idea of Flatpak.

What would they sign it with? How do you verify the signature?

Yeah just encode the files locally and rsync them to the server. You could even use a Makefile to do the conversation.

It doesn’t work fine for what it is. People use Bash for scripting all the time and it’s full of footguns and gotchas. Powershell is just an attempt at a sane shell. It’s not meant to be a full general purpose language like Python; it doesn’t make sense to equate them.

Personally I don’t really like the style of Powershell. The structured data is very obviously a good thing but I don’t really like the syntax. Nushell seems a lot nicer IMO.

bash scripting is not intended to perform all of your logic in the scripting language

Maybe not all, but it’s definitely intended to do some, and it’s really bad at it.

I don’t think it works well enough yet.

Some of us live in the real world.

I don’t think height adjustable matters. It’s more important that it’s deep (80cm+). Though I think most height adjustable desks are that deep.

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.

I think this strategy makes perfect sense and is really working.

Most of the open source community uses Linux or Mac for development. Windows is pretty much an afterthought. You even sometimes see “cross platform” projects that don’t work on Windows.

But now that you can use WSL for all that development there’s much less reason to use Linux in the first place. At my company we have a couple of hundred people using Linux, and we’re considering all moving to Windows with WSL because the hardware support on Linux is just too unreliable - random crashes, laptops not going to sleep when you close them, poor thermals, bad memory management, etc.

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.