> I guess one point I should make is that for almost every piece of software I wanted to use, I had to spend a lot of time just trying to find any that would work on Linux—then narrowing that to 'on Linux ARM64'. And then I had to usually spend a few minutes compiling it from source, placing my own shortcuts on the system (so I wouldn't have to open a Terminal every time I wanted to check Twitter), etc.

> All of these issues (4K difficulties, having to compile apps, not finding apps) are exacerbated by the fact that the Pi runs on ARM, but it is still a problem in the wider Linux ecosystem.

The point is that the above could apply to a $1500 ARM computer.

However, I suspect that he's not very experienced with Linux, and ultimately makes a comparison that doesn't make much sense.

> Anyways, on my Mac, I'm used to Shift + Option + dash for em, or Option + dash for en, but we're getting off the point.

On GTK, one can use a compose sequence for that. There you go: https://askubuntu.com/a/31265.

> All of these issues (4K difficulties, having to compile apps, not finding apps) are exacerbated by the fact that the Pi runs on ARM, but it is still a problem in the wider Linux ecosystem.

"Having to compile apps" and "not finding apps" are not problems in the wider Linux ecosystem. There's an enormous amount of stuff in the repositories of the main distros, and it's prepackaged. And there are external repos for what's not in there. The software one really has to compile manually is a very small minority (again: in the wider Linux ecosystem, that is, on x86).

For the 4K, I can't speak, as I have no experience.

Ultimately, using ARM for a desktop machine with specific software requirements doesn't make much sense; in particular, because his work(flow) revolves around closed-source software. However, that's what the explicit target of the article, so I can't really complain about it.

Edit: wrong price quoted for the 2GB model.

Nothing, just another bad blog trying to get youtube viewers.