6 ms·
This is Go's biggest problem right now. New libraries crop up and gets abandoned just as fast.
by _sabe_ 13y ago
This is Go's biggest problem right now. New libraries crop up and gets abandoned just as fast.
- cdoxsey 13y agoI have mixed feelings about this. On the one hand its true that there are a lot of abandoned libraries out there, but on the other Go isn't like node.js. They don't reinvent the wheel with every release, and changes have been very conservative (and they have tools to automatically upgrade your code for you). In general Go libraries are at their best when they follow the unix philosophy: Write programs that do one thing and do it well. Those programs, even after being abandoned for years, still work fine. (for example: https://github.com/dchest/siphash https://github.com/dchest/siphash) They're at their most brittle when they are highly platform dependent (like bindings to some C libraries) or massive never-finished frameworks.