nicr_22

Focus on open protocols, simple formats over complex vendor-specific cruft. Then you can always "fork" away from an enshittified saas.

I bet a small team of the quality of the kind developers who are attracted to hacking on Ghostty could recreate the subset of GitHub functionality they actually need in ~six months. It's just the problem of how to pay for the ongoing care, maintenance and hosting? Maybe another opportunity for Mitchell's particular brand of philanthropic OSS.

The difference here is _creative_ work vs consumption. Craftspeople like Mitchell feel passionately about the tools they rely on to build. Github has also been a social place for builders.

I don't think it's ridiculously dramatic to feel sad about great tools rusting or makerspaces closing...

Agentic ennui!

Yeah, why only _one_ fish?

It's obvious that pelican is riding long distance, no way a single fish is sufficiently energy dense for more than a few miles.

Can't the model do basic math???

There's a whole spectrum of options between super-fat React-in-Electron and expert-optimized platform-specific (perhaps GPU-rendered) apps. VS Code and Zed are close to opposite ends of this spectrum.

- slim down to a more efficient, non-virtual-DOM web stack (e. g hypermedia)

- move to a wrapper around native webview (Tauri)

- use one of the excellent cross-platform frameworks (Flutter, or that new one just open sourced by Snap)

For WhatsApp specifically, I don't understand why a company with the size and resources of Meta can't support native versions for Windows, Mac _and_ Linux. I think many people would accept non-feature-parity with the web/mobile versions, in exchange for a tight, reliable desktop messaging app...

There's a world of difference between saying "our stuff sucks" vs "here are the specific ways our stuff isn't ready for launch". The former is just whining, the latter is what a good PM does.

Interesting direction, thanks for sharing.

If you're interested in this space it's worth looking at data-star.dev. who takes hypermedia in the opposite direction - one endpoint per page, then push updates to components over SSE.

My worry with MESH is that many endpoints might become a (sorry) mess...

FlipFlopStop?

FFS for short, which has suitably disgruntled other exclamatory meanings.

Love love love Pico. It's such a terrific starting point, and easy to tweak into different directions. It's the anti-Tailwind.

Might be worth getting in contact with the Slant3D folks, their teleport 3d printing service might benefit from an integrated editor?

Just aim for the thermal exhaust shaft, you womp rat.

Radio 4 has to be Westminster, surely? And Bloomsbury in the evenings.

Richmond teeters over into Classic FM to my taste - ostensibly cultured, but basically posh-pop.

And LBC is a diffuse torroidal agglomeration of zone 3+ greasy spoons known only to White Van Men and black cab drivers.