Hey, thanks for this article, sometimes I wonder if I'm not alone, twitter & HN is literally full of hipsters and it feels like people forgot that programming is all about making tradeoffs, that there is no perfect software and that you can't ever "win", it's always about "failing the least for this specific use-case".
BTW: I've made a search engine for libraries which provides you some metrics you're describing, and when reading your article I'm actually considering adding "break factor", something like how often library gets major version incremented vs. how often it stays backwards-compatible. It's searchlibs.com if you're interested (or anybody else)
Thanks for this, really.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey, thanks for this article, sometimes I wonder if I'm not alone, twitter & HN is literally full of hipsters and it feels like people forgot that programming is all about making tradeoffs, that there is no perfect software and that you can't ever "win", it's always about "failing the least for this specific use-case".
BTW: I've made a search engine for libraries which provides you some metrics you're describing, and when reading your article I'm actually considering adding "break factor", something like how often library gets major version incremented vs. how often it stays backwards-compatible. It's searchlibs.com if you're interested (or anybody else)
Thanks for this, really.