phil

I'm noticing that just knowing my public "code/module registry" is a default rich publishing endpoint for {API} documentation, AND that this registry* will probably end up being "THE" next-50-years main code registry replacing NPM ("because web") really allows me to lean in and find the motivation to write good, clean descriptive docs inline within the code relative to each module (goodCohesion).

Also, aesthetics wise, the ~~~ with rich, contextual error reporting style ideas from things like the Rust error output, is a really beautiful trend that's emerging, and one worth emulating.

*: JSR:

I'm noticing that just knowing my public "code/module registry" is a default rich publishing endpoint for {API} documentation, AND that this registry* will probably end up being "THE" next-50-years main code registry replacing NPM ("because web") really allows me to lean in and find the motivation to write good, clean descriptive docs inline within the code relative to each module (goodCohesion).

Also, aesthetics wise, the ~~~ with rich, contextual error reporting style ideas from things like the Rust error output, is a really beautiful trend that's emerging, and one worth emulating.

*: JSR: https://jsr.io/@sys

🐵 ← 🙈🙉🙊 → /phil →  phil.cockfield.net, db.team →  
ƒ(🌳) →  🧫 /sys  ←  @cell <T>