KEYNOTE: Node.js interactive 2017 - The case for node.js
- 1. The case for Node.js Justin Beckwith github.com/JustinBeckwith @justinbeckwith
- 3. 2007
- 5. $("#chgrBar-main").droppable({ scope: 'toheader', drop: function(event, ui) { $('#chgrBar-text').html(''); if ($("#chgrBar-thumbs img[src=" + ... $("#chgrBar-thumbs").append("<img src='" ... $("#chgrBar-thumbs img[src=" + ui.draggable... } } });
- 9. We were kind of bad at JavaScript.
- 12. 2007
- 16. 2010
- 18. All I need to do is write some code that creates an HTTP request with a very long timeout and enable chunked transfer encoding. Then I’ll use another HTTP connection to send data. Then I’ll just have to write some code in C# down at the HttpHandler level that manages the state between these two connections, and then proxies the data over to an active VNC session living on another machine. Oh and I guess I’ll have to handle all the connection resets, and provide a half decent API so other developers on the team can actually use this thing.
- 23. Node.js made us fall back in love with JavaScript.
- 25. 2015
- 28. How can we make the case for Node.js?
- 30. What are the trends?
- 32. Lets limit that down to the last year.
- 34. The #1 and #10 most popular languages today are JavaScript and TypeScript.
- 35. What about code that *gasp* isn’t on GitHub?
- 38. How should we proceed?
- 39. Start small.
- 44. Get involved.
- 48. I learned a few things.
- 49. Start small.
- 51. Use data.
- 54. Sarah Novotny @sarahnovotny Open Source Wonk @ Google
Editor's Notes
- #2: Since coming out in 2009, Node.js has had a profound impact on my career. It’s shaped how I think about technology, and it’s changed the way I think about open source communities. This is a bit of a different talk than the ones that I’m used to giving. I want to share my personal story with node.js - how we got started using it on my first team, and how it’s managed to become a key part of several companies where I’ve worked over the last few years.