It's a common knowledge. Russian poet Alexander Griboyedov[1] wrote a poem about this paradox - Woe from Wit[2]. Note, that in this poem it's a satire, but it was still tongue-in-cheek title that reflects the real phenomenon.

[1] https://en.wikipedia.org/wiki/Alexander_Griboyedov

[2] https://en.wikipedia.org/wiki/Woe_from_Wit

Something like ELinks could be created by writing a simple TUI on top of the Servo engine. Then it would be able to handle even complex Web pages full of JavaScript which is a huge chunk of the modern Internet.

With famously weak energy grid[1], South Africa would certainly benefit from the same approach. Sadly, it seems, it isn't considered en masse.

[1] https://en.wikipedia.org/wiki/South_African_energy_crisis

I think we should aim for Ceres[1] instead, which is way more resources rich compared to Mars for a sustainable colony. And a perfect starting point for exploring the rest of the asteroid belt[2].

[1] https://en.wikipedia.org/wiki/Geology_of_Ceres

[2] https://en.wikipedia.org/wiki/Colonization_of_the_asteroid_b...

The weakest point of any robot now is the energy source. Even with the most advanced AI and body it will be tethered to the power network or some big battery. It will negatively affect potential adoption outside of the places like warehouses, factories, hotels, malls, bars, etc.

Tethering worked for Evangelions tho

The question is if they figured out that the robot needs to run off two batteries so it can swap them out of itself, or not.

There's a way better solution for self hosted email these days - Stalwart[1]. Supports all necessary protocols and extensions, including modern JMAP. And, of course, it's memory safe, unlike Postfix and friends.

[1] https://github.com/stalwartlabs/stalwart

There is still continued work on LaTeX3[1][2], but it took so long without any release[3], by this time not sure if it will get adopted.

[1] https://www.latex-project.org/latex3/

[2] https://github.com/latex3/latex3

[3] https://tex.stackexchange.com/questions/572113/whats-the-cur...

LaTeX3 has either been cancelled or has already happened, depending on how you look at at. [0] But despite that, LaTeX is still continuously improving, although it will never beat Typst on speed or simpler markup.

[0]: https://www.texdev.net/2024/11/11/the-mythical-latex3

Long term QoL definitely needs money: healthy food, means to exercise, enough time and freedom for work-life balance, travel, and so on. So yes, money are necessary for it. But the amount has a certain cap, let's say somewhere between $1-30M depending on the place where you live and the size of your family.

First, they should move to GitHub or GitLab (or Codeberg) to attract more contributors and make the process of development easier. Maybe it could also be ported to support Wayland and Unicode properly, and remove some legacy code to ease up the maintenance.

Just migrate to Forgejo/Codeberg[1][2] or SourceHut[3]. Both are like a light speed compared to GitHub and GitLab.

[1] https://forgejo.org

[2] https://codeberg.org

[3] https://sourcehut.org

I think Forgejo is great. But we need to remember the fact that many enterprises pick GitHub or GitLab because they provide paid support and SLA. Also Forgejo Actions are still in beta, while GitLab and GitHub are pretty established solutions for CI/CD

Sourcehut is basically a really barebones web interface for git server, so I don't think it's really comparable to GitHub

For hosting your own projects that's sometimes not a viable solution either. Limiting your open source project to platform other than GitHub hurts it's discoverability, because usually GitHub is what most devs and non devs associate with open source. I heard a lot of "It's not open source if it's not on GitHub". You can mirror your project to GH of course

"Just migrate to X because it's faster" doesn't work that well in the real world

My forgejo-server ran on a broken fiber for a few weeks - we're talking about speeds in the single kilobits/s. It kept up fairly well!

Pushes and pulls would still kinda work, actions not so much (but that's cause it needed to transfer more then 100MB)