Gleam might be a great choice perhaps. Compiles to typescript and Erlang/BEAM.

I like alternatives to formal IT lawfare, like CUPID [0] properties for Joyful coding by Dan North, as alternative to SOLID principles.

[0] https://cupid.dev/

We had a large green plant growing in an unused fridge. Fungus yes, but this was a new experience. As students we learned a lot.

Borax is an example of a substance that is simultaneously used for skin care, household cleaning, as soldiering flux, and ant killer. But I guess it is a constant with variable effects. Hard to be found in local shops anymore.

reminds me of WD-40 (water displacer formula 40).

not used that often to displace water.

Really? It's at practically every hardware store I've been to (US, things may be different elsewhere).

Yes, Netherlands, think it is quite different in retail in comparison.

Blog got the hug of death, I think. Archive link: https://archive.is/bpNAw

It wouldn't be that weird a thought for me that, preferably a group of, nation states cough up some serious money and give this a real start, beginning, and end in the form of a stable release. This already happens with major science and space projects, with budgets of billions. A browser is not simply a bunch'a software, having a modular open browser is a major deal and benefit to society at this point. Perhaps arguably more valuable than pumping yet more energy in a particle accelerator and other of mankind's pet projects in search for the unknown unknowns and deal with more pressing known knowns first.

> preferably a group of, nation states cough up some serious money and give this a real start, beginning, and end in the form of a stable release

It doesn't take serious money. It takes a constant stream of "sub-serious" money, stable for a long time.

A large city could pay for that project. It doesn't take a group of nations, what it takes is non-standard politics.

I love this idea!

Or - there was a HN discussion on this half year or so ago - there's consolidation again, and there will be AI, but no code. Domain expert talks to the AI, perhaps with an expertised intermediary. AI spins up a whole new 'software platform' for the customer.. internally. Offers all the UI that is needed to work with it.. still 'in the cloud' i.e. in AI data centers. Customer happy, devs less happy.

Wasn't the whole Penpot UI itself made in SVG? Or did they change that along the way?

For S3 self-hosters check out Garage, who are developing with NLnet funding: https://garagehq.deuxfleurs.fr

Covered by the article:

>I ran local experiments with Minio, SeaweedFS, and Garage. My primary objection to all of them was the operational complexity

Out of the listed options, Garage is actually really simple for something that runs on multiple servers. It was also the only easy option I found that can replicate over WAN and isn't super latency sensitive.

Wow, it surprises me that there aren't more comments on this zine, which I find a delightful way to present interesting CS topics, detailed explanation and pages full of explanatory drawings that speak. The Zines page [0] mentions the definition of a zine:

> "a small-circulation print or online publication that is produced through noncommercial means and is meant to appeal to a niche audience"

So then, is "causally ordered message delivery", "introduction to choreographic programming", and "Fighting Faults in Distributed Systems" too niche for HN? Hand-crafted with human sweat and tears, no AI. Is that the reason then perhaps for the silent comment thread, i.e. TL;DP, "too long, doesn't prompt"?

[0] https://decomposition.al/zines/

I've read through ItCP. The illustrations were wonderful, but I was rather annoyed by the typeface.

... And somewhat disappointed by the conclusions. A Java compiler (sans an overview of limitations/capabilities, but I understand the limitations of the format), and a... Haskell library, which, unfortunately, is incredibly irrelevant to me.

How is this subject approached in practice? I'm fairly familiar with authentication (generally handed off to a bespoke service + library that abstracts away most of this for the end programmer), but my generalist experience with other coordination problems between distributed systems is that programmers tend to not be particularly rigorous about them - and try their best to break down cross-service relationships to very, very simple-to-implement-in-a-bespoke-fashion cases.