Rags to Open Source - AllThingsOpen, Raleigh, NC 2014
2 likes572 views
The document discusses the journey of the open-source MVC framework Sails.js, highlighting its inception in 2011, numerous downloads, and growth within the developer community. It emphasizes the importance of community support, feature requests, and maintaining clear documentation. Key takeaways include the necessity of writing only needed code and differentiating between support and marketing efforts.
Rags to Open Source - AllThingsOpen, Raleigh, NC 2014
- 1. from rags to open-source Raleigh, North Carolina 2014
- 2. Mike McNeil @mikermcneil github.com/mikermcneil
- 3. bdfl of the leading open-source MVC framework for Node.js
- 4. the leading open-source MVC framework for Node.js
- 5. over 1 , 5 0 0 downloads / day 8,030 GitHub stars at least pageviews 830,000 since 2013
- 10. (us) (customer) (Javascript app)
- 11. Node.js... love at first sight circa 2011
- 12. “We’re doing I/O completely wrong.”
- 13. “Not acceptable!” <— “just look at the Unterschied!”
- 14. “Concurrency should be easy.” “Threads should be used by experts only.”
- 15. How is that possible? (copy the browser)
- 16. // synchronous! console.log(‘hi’) vs. // asynchronous! setTimeout(function (){! console.log(‘hi’);! }, 240000000); incredible
- 17. I wondered… could we use …for everything?
- 18. so…
- 20. You don't want to be writing all these system calls. You need something that gives you… an ORM abstraction, or something.
- 21. so Sails.js was born
- 24. Sails is an MVC framework.
- 25. Sails is an MVC framework.
- 26. Sails is an MVC framework.
- 27. Sails is an MVC framework.
- 28. Sails is an MVC framework.
- 29. Sails is an MVC framework.
- 30. Sails is an MVC framework.
- 31. Sails is an MVC framework.
- 32. first version (late 2011)
- 33. December 2012
- 35. >=20 other community adapters custom app-specific adapters
- 36. http://web.archive.org/web/20130514080123/http://balderdashy.github.io/sails/ first halfway-decent docs January 2013
- 37. posted screencast in early 2013
- 38. …woke up to 1000 views
- 39. reddit — Feb 2013 hacker news — Mar 2013 and again two months later
- 41. managed to get sailsjs.org online mid-spring 2013
- 42. issues pull requests questions
- 46. ????
- 47. ???????????
- 48. v0.9 introduced a new streamlined asset pipeline
- 49. asset pipeline???? asset pipeline????????!!!! “what about gulp?!” “so thirsty…” asset pipeline????????!!!! asset pipeline????????!!!! asset pipeline????????!!!! asset pipeline????????!!!!
- 50. so v0.10 introduced generators.
- 51. feature requests are the hydra
- 52. they will never stop.
- 53. they will never stop. ever.
- 54. moral of the story
- 55. only write code you actually need if someone else actually needs something, they’ll write a pull request only merge new code if someone actually needs you to merge it (i.e. there’s no other way, via a plugin or something)
- 60. #sails on freenode (IRC) issues groups
- 62. • Github stars • NPM downloads / day • Google group membership • IRC channel activity • Number of tagged StackOverflow questions (and your answer ratio)
- 64. inline jsdoc comments are not enough write docs in markdown compile to HTML
- 65. DRY don’t repeat yourself
- 66. the goal of open source DRO don’t repeat ourselves
- 67. so make an IRC channel start a Google group post a YouTube video
- 68. but remember support !== marketing
- 69. support !== marketing ( ) but remember
- 70. ∃ far more front-end developers than back-end developers
- 71. ∃ far more front-end developers than back-end developers eventually everyday backend development will be commoditized
- 72. Questions?
- 73. from rags to open-source @mikermcneil