Nostr Web Client

legacy build environments were intended for "full stack" engineering, which is largely irrelevant in the nostr age. In the nostr, to read you need WebSockets and to write we need secp256k1. that's it, that's the beauty. This simplifies a lot of the engineering, making the nostr evolve rapidly. The data is fixed, but how we display it changes over time.

nobody 1y ago

Unless I’m missing something, to do anything useful you would also need a UI library, a JSON serialization library (assuming you’re using not jabbascript) and probably a DB library as well.

Reply to this note

Please Login to reply.

Discussion

MichaelJ 1y ago

This is all true. And honestly it's the UI and DB stuff that's the hardest.

Laeserin 1y ago

You're missing the fact that they're not building anything useful.

Lucid 1y ago

Fuck json

Laeserin 1y ago

Yaml?

Laeserin 1y ago

XML 🙈

Lucid 1y ago

BSON

Luxferre 1y ago

TSV. Plan9's NDB. GNU Recutils. Bencode or even djb's netstrings.

Plenty of formats that require less computing power to manage and less effort to read. Yet the hindustry settled on JSON/YAML/XML.

Laeserin 1y ago

Best format doesn't always win because of network effects.

Luxferre 1y ago

I doubt any efficient data serialization and marshalling formats, as well as fast and efficient software in general, are ever going to be widely adopted unless a global energy crisis occurs and everyone is forced to live on 40W max per desktop.

Matt 1y ago

this is a mostly hot take, but HTML+CSS is a UI library, and JSON.stringify is included. Why need db?