Depends what you use and how you use it. With how I use my computer, I have issues on Windows that require terminal input to solve and are more confusing than many of the Linux issues I face, but the way I use Linux also requires terminal. Some applications just work better or only on terminal whether you’re on Windows or Linux and some debugging steps will inevitably take you down the dark road of decade old menus and terminal commands.

Day to day basic tasks though? It shouldn’t need any special knowledge, provided that you don’t follow the wrong online tutorials like I did when starting out. For example, Firefox was out of date so I looked up how to update Firefox. The package manager did not have a new version and I didn’t think to manually go into settings and refresh the repository (stores auto update, right? Well, no actually…). Basically I ended up trying to install via a .deb package from their website… it didn’t work and I felt Linux was dumb. What I should have done was update my OS and package manager first or simply sudo apt update && sudo apt upgrade (yes this is terminal, sorry). My point is, sometimes you have to realise the question you are asking is flawed and not the system.

I actually think the poor branding is part of why Mastodon is hard to spread. Can you picture anyone seriously saying they “tooted” something? Because I can’t.

Oh! Well that’s awesome then, thanks for the correction. I did look it up but ended up on some “top feature” article which barely mentioned any features beyond layer multi select. I should have looked further.

Still no smart objects/non-destructive editing? :(

Well a good indicator is if I have to check the source code of a packaged program to understand what something does, the documentation is not good enough. And yes I’ve had to do this far too much.

I agree, but I don’t think images should be relied on as the primary communicator. I have seen far too many forums/websites/docs with broken images because the host went down. That and archivers are more likely to fail at saving images. Explain it using text and give a reference image to further display the point.

You don’t have to… if the project you want to use has a good setup process. Otherwise you’ll be scouring Docker docs, GitHub issues, and StackOverflow for years.

Training users to click on this shit is the same reason people wipe their desktop by ignoring “Yes I know what I am doing” warnings.

File format? mkv, so convenient. But media codec would be h265 any day. I find the video quality to file size to be perfect for most films and only have issues with it on the largest files and the lowest power hardware (Roku TV). For the movies I really love and rewatch I sometimes get h264 for the better visual quality. I tried some AV1 files and found the artifacts really ugly, but admittedly these were very small files. That and the lack of hardware decoding on most hardware is preventing me from migrating.

The limits don’t matter if the provider raises their price next month.

Krita is a drawing-first program, so this makes sense.

I would bet money that phone makers such as Google keep storage low to steer people towards their cloud storage options.

I would happily use one for my music and movies to access them on the go. I already have copies elsewhere, so it would be no big loss if the card died.

They are, but mostly in budget phones. If you want a flagship camera or processor as well, you’re sadly out of luck. And god forbid you want a folding phone.