Yeah initial WASM downloads are a kicker; though once you cache the download (like with a Service Worker) it should be a one-and-done thing. I've been seeing SQLite+WASM-powered web apps and web apps boosted by the local relay tray as two sides of the "edge". Bring compute and storage down to the end-user's device either ad hoc with WASM in the browser or more intentionally by asking them to download an app. Either way it decentralizes compute almost as far as possible.

Especially the package management. Use Bun as a package manager and Node as the production runtime and you still get a vastly better DX than NPM.

Bun is straight 🔥 Some benchmarks put its performance within spitting distance of garbage-collected languages like Java, C#, and Go. For a JS/TS runtime, that's really impressive.

I'd be curious to see performance benchmarks between IndexedDB and SQLite WASM. You'll have to use shared workers pretty heavily, but that gives true parallel processing across tabs, rather than just concurrent work on a single OS thread.

Makes total sense. What will you use for storage? IndexedDB?

Yeah I don't expect they'll try to compete directly with AWS or Azure or GCP. If anything, they'll host workloads on Azure, since they recently inked a deal for billions in Azure compute. The business model I'm thinking of is more like Deno Deploy. Runtime + serverless hosting model + (in Anthropic's case) first-class integration with Claude APIs. There are innumerable VC-backed startups that would pay for such a service that gets their ideas up and running that much faster.

With its acquisition of Bun, I believe Anthropic is setting itself up to become a vertically-integrated cloud hosting and web services platform for AI-powered apps. Just training and providing LLMs isn't profitable. Big players like Google can swallow the costs without blinking, but new players like OpenAI and Anthropic have to pivot to providing services to balance their books. https://bun.com/blog/bun-joins-anthropic

I've been working out similar processes on my new project. I spent several sessions writing documentation, deciding on architecture, setting standards, and planning before writing a line of code. Now, I have a solid plan and can move pretty quickly with AI generating much of the code.

Planning to use service workers in the browser? Also, are you thinking one connection per relay? Most Nostr apps use multiple relays simultaneously. How will it handle deduplication on multiple overlapping data streams from different relays?