stop making backwards incompatible changes to the protocol ffs. can't we move fast without breaking things?
Login to reply
Replies (9)
Moving fast and breaking up things is kind of what we do ๐คฃ
Where did this happen?
All over the place
Such as?
๐
Lmk if you want me to log breaking changes on nostrability issues and/or create JSON validation schemas for a particular kind
And what about libraries used to build nostr apps? They change function interfaces every other day in minor version increments... It's like an eternal v0.0.0.1...
I've been complaining about that too. Highly recommend applesauce by @hzrd149 since he does semantic versioning right and provides migration guides in the docs. NDK and nostr-tools have the problem you mentioned. So frustrating as a client dev.
NDK? He doesn't even have a changelog, so he releases a new version and you don't even know what the changes are unless you want to review each commit... Documentation unmaintained, issues unmaintained...
I didn't know applesauce, so I'll give it a look, but I've been giving a look to SNSTR, and I cannot wait to migrate to it, as it seems like it's a 1000x improvement over ndk/nostr-tools...
emphasis in _kind_