cosmicbytes

Thank youu!! I'm so glad that you like it :')

Different software.

Slightly related: my own blogpost about demistifying containers. It takes a quite different approach from the OP and focuses on a different side of containers. Would appreciate any feedback!

https://cosmicbyt.es/posts/demistifying-containers-part-1/

This sounds very similar to "rash" which is based on racket

The name conflicts with the build tool used for ocaml, which is also called dune.

I wish s-expression was a popular alternative. It's readable without the yaml issues.

You're right, and I actually make that point in the blog post! Reactivity is not exclusive to the frontend.

However, in the frontend, Reactivity is almost an invisible default. You don't opt into it, you just kinda have to when you use a modern framework.

In the backend, many people use Reactive patterns without even knowing them or thinking of them. But either way, if you do use them, you likely opted in, and it wasn't a "all code you write is automatically reactive" like in modern browser ui frameworks

I thought the point of a CDN is that its available at edge locations. Do you have multiple servers geographically dispersed? If so, can you explain what else makes it a CDN?

Sorry if my comment comes off as snarky, when I read it, it sounds like that, but I promise it is not my intention!

I like Podman, but I still have trouble making two rootless mode containers be accessible to each other through network communication.

Time saved is not the most important part. Here is my opinion:

• it is very satisfying to use. Once it becomes muscle memory, vim just gets out of your way, and you feel like you're one with the computer. Your ideas flow freely from brain to document.
• neovim is highly customizable and scriptable. You can make it do many things, many of which were never even conceived by the developers.

Have you considered raku? I'm not super familiar with perl but I assumed raku is perl improved

What a great blog. Thanks!