TCP/IP: the past
NOSTR/FIPS: the future
nostr:npub1hw6amg8p24ne08c9gdq8hhpqx0t0pwanpae9z25crn7m9uy7yarse465gr nostr:npub19wavu4f7l6l43h24jyskn7fvzy37kcfp67aqjtmv2qgy4lp34nhsda8p6k
I was going to ask if you were referring to the Alpha 0.1.0 project, but saw you tagged jcorgan, so answered my own question. (jmcorgan/fips).
I'm curious how you see the evolution of software toolchain ecosystems outside of TCP/IP. (Rust in particular is heavily invested.) Of course, nobody would say the old stuff is going away, but if you have to bridge and build everything through legacy, I'm not seeing the advantage. (Just send those KIND-1 notes around Nostr-over-FIPS after building and maintaining gigabytes of toolchain over legacy TCP/IP? Sending JSON event objects?) I forget the article, but I was reading recently about the insane amount of corporate money going in to handle these toolchains (NPM, Rust/crates... on and on).
I'm curious how you see the evolution of software toolchain ecosystems outside of TCP/IP. (Rust in particular is heavily invested.) Of course, nobody would say the old stuff is going away, but if you have to bridge and build everything through legacy, I'm not seeing the advantage. (Just send those KIND-1 notes around Nostr-over-FIPS after building and maintaining gigabytes of toolchain over legacy TCP/IP? Sending JSON event objects?) I forget the article, but I was reading recently about the insane amount of corporate money going in to handle these toolchains (NPM, Rust/crates... on and on).
1