4 ms·
I've gotten so tired of protocols and specifications that are overly complex or are poor fits for how they're used that I've started developing my own for the s
by kstenerud 7y ago
I've gotten so tired of protocols and specifications that are overly complex or are poor fits for how they're used that I've started developing my own for the services I'm implementing [0].
Making protocols & specs no more complex or ambiguous than necessary is a hard requirement in this modern, security-conscious world.
[0] https://github.com/kstenerud/specifications https://github.com/kstenerud/specifications
- amelius 7y agoWho else is using your specs?
- kstenerud 7y agoI couldn't say; Github doesn't report to me who is including my code or implementing my specs. The point is to make specs that people actually WANT to use, which requires advocacy (to get more eyeballs on it), and collaboration (to fix things I've missed). I build these things to scratch an itch, but I want others to find them useful, as well.
- kennyadam 7y agoReminds me of this XKCD https://xkcd.com/927/ https://xkcd.com/927/
- kstenerud 7y agoIf it does, then you've misunderstood what it means. It's about "god" standards, designed to encompass all other standards, a theme common in the 90s.
- kennyadam 7y agoI'd argue that it can apply to any situation where someone is unhappy with the current set of solutions, decided to create a better one for people to use, but simply ends up adding another one to the pile and increasing the convolution.
- javajosh 7y agoNeat, but I strongly recommend a "related" section in your list of pointers. One of the best ways to communicate what you've made is to relate it to things people already know. E.g. is this thing like Protobuffs or like Markdown? Is it like a Merkle Tree or like Moment? Another valuable thing this does is give people looking for an alternative technology a way to find your thing.
- kstenerud 7y agoThat's a great idea! Thanks!