Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

KEYNOTE: Node.js interactive 2017 - The case for node.js

451 views

Published on

Node.js has had a transformational effect on the way we build software. However, convincing your organization to take a bet on Node.js can be difficult. My personal journey with Node.js has included convincing a few teams to take a bet on this technology, and this community. Let’s take a look at the case for Node.js we made at Google, and how you can make the case to bring it to your organization.

Published in: Software
  • Be the first to comment

  • Be the first to like this

KEYNOTE: Node.js interactive 2017 - The case for node.js

  1. 1. The case for Node.js Justin Beckwith github.com/JustinBeckwith @justinbeckwith
  2. 2. 2007
  3. 3. $("#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... } } });
  4. 4. Testing was hard
  5. 5. Lack of prescriptive patterns
  6. 6. Browser inconsistencies
  7. 7. We were kind of bad at JavaScript.
  8. 8. 2007
  9. 9. 2010
  10. 10. Gateway VNC PROXY
  11. 11. 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.
  12. 12. Node.js made us fall back in love with JavaScript.
  13. 13. 2015
  14. 14. Java C++ Go Python
  15. 15. How can we make the case for Node.js?
  16. 16. What are the trends?
  17. 17. Lets limit that down to the last year.
  18. 18. The #1 and #10 most popular languages today are JavaScript and TypeScript.
  19. 19. What about code that *gasp* isn’t on GitHub?
  20. 20. How should we proceed?
  21. 21. Start small.
  22. 22. Measure. Improve.
  23. 23. Get involved.
  24. 24. I learned a few things.
  25. 25. Start small.
  26. 26. Solve real problems.
  27. 27. Use data.
  28. 28. Grow involvement.
  29. 29. Sarah Novotny @sarahnovotny Open Source Wonk @ Google
  30. 30. THANK YOU @justinbeckwith @sarahnovotny

×