We fail to follow SemVer – and why it needn’t matter

Given at http://www.nodejsdublin.com/

1. ☺ Hi, I’m Stephan @boennemann @boennemann
3. 170,000 @boennemann packages on npm
4. A package is a solved problem @boennemann
5. 1. npmsearch.com 2. npm install <package> 3. ? 4. profit @boennemann
6. X.Y.Z @boennemann Major Minor Patch http://semver.org
7. @boennemann Major Minor Patch http://semver.org 1.0.0
8. @boennemann Major Minor Patch http://semver.org 1.0.1
9. @boennemann Major Minor Patch http://semver.org 1.1.0
10. @boennemann Major Minor Patch http://semver.org 2.0.0
11. 2.0.0 @boennemann Major Minor Patch Breaking Feature
12. 2.0.0 @boennemann Breaking Feature Patch http://semver.npmjs.com/ ~ ^
13. Nein @boennemann
14. We fail to follow SemVer @boennemann
15. @boennemann http://npmbynumbers.bocoup.com/ 0.y.z >0.y.z
16. Anything may change at any time @boennemann
17. @boennemann
18. No changelogs @boennemann
19. @boennemann
20. Hauptversionsnummern- erhöhungsangst¹ @boennemann ¹ Fear of increasing the major version
21. If we strictly followed “semantic” versioning, it would probably be Backbone.js 43.0.0 by now — which doesn't help anyone evaluate the actual progress of the project. – Jeremy Ashkenas, http://backbonejs.org/ @boennemann
22. evaluate the actual progress of the project @boennemann
23. Versions are not for humans @boennemann
24. @boennemann
25. @boennemann 1.x 2.x
26. @boennemann 1.x 1.x
27. Versions are not for humans – names are @boennemann
28. Our tools are so bad, we value human readability in computer protocols when it really doesn’t. fucking. matter. @boennemann – Stephan Seidt, http://fucking.engineering/
29. We fail to follow SemVer and why it needn’t matter @boennemann
30. live-coding @boennemann
31. ⭐⭐⭐ git.io/semantic-release npm.im/semantic-release @boennemann
32. Thank you @boennemann