Jakob

Oh interesting that got reformed, too! Strange choice to split it in two instead of three words (the latter which would have mimicked English: “all too”).

Well, then it seems we don’t have any single German word for all too regular anymore :(

I would go with “allzuregelmäßig”.

Similar to “allzuschön um wahr zu sein”, “allzugroß” etc.

Very nice article. Refreshing to see one liners and fun projects. And the website’s glamour mode is great, too.

Although, as tradition requests, any example of the useless use of `cat` (UUOC) must be called out. The _much_ more efficient use would of course be

  tr '\n' ' ' < input.txt | tr -d '\r' | fold …

I still have the original iPhone lying around. I really like its design but it’s too slow and the software too old.

I was always wondering whether a thin client concept like this could bring it to live again.

Submitted, because I just found out that even after 28 years, the definition of "upstream" and "downstream" is still heavily contested.

> Umm, no. Fix the Envoy proxy terminology so that it isn't obviously wrong.

Yes, Singapore is great for that. But to be fair with the other cities, it’s very hard _not_ to have abundant vegetation in tropical rainforest climate. Everything grows rapidly and stops at nothing in its way.

In other climates, like European ones, this becomes much more complex. Germany struggles even to keep its forests alive with long stretches of missing rain, higher temperatures, and new pests. Single trees in cities constantly die. Spain is in large parts a desert etc.

I really hope we find a solution/adapted plants to keep cities from heating up so much.

I would see that as an absolute win. Socialization is the main point I send my kids to school.

Socialization leads to discourse which leads to learning.

I really like Mimestream, which is a native client for Gmail.

Very fast and supports all the usual native macOS keyboard navigation, e.g. shift or command to amend selection in a list.

Maybe not in your corner of the internet, but businesses used server side includes (SSI) for that, not iframes.

You add “include” tags to your HTML file and your web server like nginx or varnish would replace it with the fragment at runtime.

  <!--#include virtual="../footer.html" -->

I saw this was quite popular for big publishing houses with millions of articles still relatively recently 10 years ago. They would only write the HTML body of a new article and the other fragments would be included by the web server.

Very cheap, stable, and very big changes across the whole website could be done instantly since cache invalidation is trivial (the web server knows all modified dates of all fragments).

Also, no additional CDN or caching needed. Later, with CDNs there was even a variant where these fragments were hosted at the edge (ESI).