Google is no longer interested in returning good search results, their priority are ads. (Good results are on ads)

I use acme as a personal wiki where I can store useful playbooks (executables from there). From sqls to kubectl commands. Just a big wiki with the unix at the mouse.

Perhaps we need an expert on design history. Typefaces are a complex thing with lot's of design decisions behind.

At my past job we have something like for newsletters and 250k/tasks per day was fine. The only design problem we have had is that if you keep past tasks on the queue table, when it grows it traches a lot cache due to index writes, so moving already finished jobs from the hot table had solved the issue.

This is one of the firsts principes of critical thinking: it's not only about understanding something, it's about being ready to challange it.

We do something like this, also we took some inspiration from hashura. Asyncpg it's so fast an ergonomic.

That sounds great! I’ve always kept an eye on how Hasura does things. Do you have any open projects using this stack?

Think on it like a middleware that wraps a transaction. It's fine, till you start consuming other Io based services (elastic/solar/...) And you find that this blocks one connection per request..

Synthetic event system + render decoupling. Preact uses the event system of the platform (browser) and only renders to it (there's no react native support).

Anyway we are using it at prod and allowed us to reduce our bundle sizes ;)

Worth noting that while Preact specifically doesn’t support React Native, JSX does. So to the extent the dev APIs stay in line you can always swap out the underlying library for that target (or other renderers).

Also it'so easy to start making new components dependent on the store, and ending with reusability.

I'm more used to preact, it's small it's fast, and it's near the DOM. Last, with preact/htm it doesn't need any tooling :)