foothall

Watch a casual users use a website or program, and for the most part they stumble their way through.

Only via good design do they stumble in useful directions.

Developers have better models how the program/website is arranged and so don't need good design as much, and see overt styling as noise.

(I spoke in absolutes for brevity. Exceptions will apply.)

I used Qubes for a few years, but gave up due to having weak control over the VM templates, and difficulty playing games.

Using Qubes would allow you to familiarize yourself with VM-oriented workflows.

I'm not particularly worldly or knowlegable, but I occasionally read non-fiction books and Wikipedia to learn.

I find the news to be too event-oriented.

I use RSS to keep up to date with some tech fields.

I'm impressed how quickly Cloudflare write these educational articles during incidents.

I suppose them prioririzing it acts as good marketing?

Thanks. The OP of the link relates to the high bar that Alacritty has for contributions.

I can understand this helps to keep Alacritty manageable. Leading projects sometimes involves saying no to features, as they do: https://github.com/alacritty/alacritty/issues/1309

That's just a tradeoff.

I see. Poor MacOS support isn't indicative of an unhealthy project, but I can see why MacOS users might want to avoid such projects.

https://github.com/alacritty/alacritty/issues/1561#issuecomm... describes why the maintainer thinks the opinion was entitled. I don't think your description is accurate.

I don't know anything about Alacritty.

What is unhealthy about the project?

+1.

This can lead to corporate capture. We see this in some projects already.

I enjoy the Linux mobile space: https://linmob.net/ is a good blog to start.

That community happens to be interested in other topics such as decetralization and repairable hardware too.