This

Effect-like code without Effect (to some extent) evolu.dev/blog/effect-li…

David K 🎹 I would use `NonEmptyReadonlyArray` instead, but then we could have another problem: we might lose' NonEmptyReadonlyArray', so what then?

MJ One of the reasons I'm working on Evolu | local-first that scales is to avoid server and cloud complexities. Sure, we need servers/clouds, but the less, the better.

Cory House Pavel Svitek 🇨🇭 Travis Watson Cory House Then have a look at Evolu | local-first that scales, it uses SQLite and their latest version can do syncing quite well, see blog evolu.dev/blog

To me, local-first is more of an economic issue than a technological one. Of course, we need tech, but that’s not everything. What I see, and what wasn’t mentioned in the original article from Ink & Switch, are the economic consequences of centralized client-server software.

Complexity is the worst kind of vendor lock-in.

Evolu now uses EEPs – Evolu Evolution Proposals – to plan and discuss features before implementation. The goal is to keep changes thoughtful, stable, and open to feedback. EEP-001: Ephemeral messages → github.com/evoluhq/evolu/…

A Relay (a dumb server): - knows nothing about clients - syncs only data - is as simple as possible I believe this is the correct approach to what Martin Kleppmann calls “the local-first endgame”

Local-first app store! Damn! 🩶

200⭐️! 👶👣

Aden the Cat kysely ... bsky.app/profile/kysely.dev this is our Bring Your Own SQL Knowledge design principle in tweet form. 🍻

Local-first and open-sourced Grammarly, nice! writewithharper.com

Building Nostr A guide for developers building on the decentralized social protocol building-nostr.coracle.social

The Copy‑Paste TypeScript Standard Library ⬇️

Aliaksandr Valialkin Tim Sweeney For loop debugging is also much easier, I don't even know what the context is when I enter functions like map filter.