Thread

Zero-JS Hypermedia Browser

Relays: 5
Replies: 8
Generated: 04:14:17
The real documentation is the written code. It is always up to date. The code is more than that. The code is the specification of the program based on the compiler of the language it is written in. Different compilers might create different interpretations of the spec. LLMs will be able to quickly answer questions based on the code. Traditional documentation is a lot of work to keep up to date and often they are not adequate for either beginners or experts and sometimes they lack specificity or might even contain inaccuracies. Code as docs and spec is the future the better LLMs get.
2025-05-06 17:28:25 from 1 relay(s) 5 replies ↓
Login to reply

Replies (8)

browser vendors already dont agree. there are still plenty of differences between them. they grew out of a time when standard bodies were how specs are done. today things are different, but even BIPs and NIPs and the likes are still not making source the spec. LLMs arent on the level yet to reliably generate human readable docs or specs from source, leave alone diff implementations to figure out the differences. ...but i'd say its where things are heading and i think thats a good thing 🙂
2025-05-06 21:05:10 from 1 relay(s) ↑ Parent 1 replies ↓ Reply
no. ideally instead of writing a NIP, you would implement a module and then use it. Basically the same way you would use a crypto library instead of rolling your own. Of course, anyone can implement a compatible version and maintain it and track upstream changes.
2025-05-07 17:22:49 from 1 relay(s) ↑ Parent Reply