Let's Make Javascript Great Again!

Interactive session at SXSW 2017.

Transcript

1. Let’s Make Javascript Great Again #makeJSga
2. Do you wanna make JavaScript Great?
3. Do you wanna make JavaScript Great? Easy!
4. jQuery Backbone Ember Angular React vue.js
5. HTML XHMTML HTML5 Handlebars Jade JSX
6. 6to5
7. ES5 ES6 CoffeeScript ES7 ESNEXT 6to5
8. ! ES5 ES6 CoffeeScript ES7 ES2016+ CommonJS or AMD modules!
10. CDN dependencies Bower NPM <- So 2015!
11. CDN dependencies Bower NPM <- So 2015!
12. Grunt Gulp Broccoli Mimosa Makefiles webpack
13. Grunt Gulp Broccoli Mimosa Makefiles webpack SystemJS
14. Grunt Gulp Broccoli Mimosa Makefiles webpack SystemJS fetch promises await Exponentiation operator Array.includes Classes Object enumerable arrow functions Generators global import Async ivate fields trimStart trimEnd 
 promises f and from string Nested im Observa string.ma Relations cons let sessionSt Template s
17. How did JS get here? Can we make JS better? Why JS can be great.
18. David Woody Conrad VanLandingham @davidjwoody @conrad-vanl
19. Our Story
20. Startups + Meteor Our Story
21. We help companies build products like startups. A Digital Product Innovation Agency
22. Rapidly unlock value for good people with meaningful ideas +1 for JavaScript!
23. How did JavaScript
 get here? How? Can? Why?
24. How did JS get here? JavaScript built by Brendan Eich (who’s speaking right now at the Hyatt Regency, better run!) for then , First delivered prototype in 10 days, circa 1995
25. 90s - 2000s The Browser Wars How did JS get here?
26. How did JS get here?
27. Eric Schmidt, CEO Google "It was so good that it essentially forced me to change my mind." How did JS get here?
28. 2008-2009 Birth of Node Open Source V8 Engine (2008) JavaScript on the Server (2009) How did JS get here?
29. How did JS get here? “Learn Once, Write Anywhere.”
30. Github Popularity StackOverflow Popularity Objective-C Ruby C C++ Python PHP C# Java JavaScript Today Most popular dynamic language (Yes, this is to scale) How did JS get here?
31. - Person who said this How did JS get here?
32. How did JS get here?
33. How did JS get here?
34. • Coherent model for development • Module system / code separation • Declarative data binding • Components, routing scheme, • data validation, animation, event management, etc • Community support = stability, new features, OSS Frameworks provide: How did JS get here?
37. 2016 97% growth over 2015 As measured by Comparing community activity on open source projects
38. Can we make
 JavaScript better? How? Can? Why?
39. Can we make JS better? How is JavaScript not great today? • The “new framework every day” fatigue? • The “language was built in only 10 days” hindsight?
41. JavaScript’s rise through convictions Can we make JS better? • Forced to grow in hostile browser wars • Lack of new ECMA versions for a decade • Open source community having to “fix” and grow the language
42. If it can be written in JavaScript, it probably will be written in JavaScript. Can we make JS better?
43. How? Can? Why? Can we make keep up with
 JavaScript better?
44. Don’t invest in a lot of up-front technical debt (ie… big boilerplates). Understand what the different libraries in your packages.json actually do. Focus on how data flows through your app. Can we make keep up with JS better? Keep It (Stupid) Simple.
45. Any dependency you bring on to a project is just as much a liability as if your team wrote the code. Can we make keep up with JS better? Evaluating Open Source Libraries
46. Can we make keep up with JS better? module.exports = leftpad; function leftpad (str, len, ch) { str = String(str); var i = -1; if (!ch && ch !== 0) ch = ' '; len = len - str.length; while (++i < len) { str = ch + str; } return str; }
47. Can we make keep up with JS better?
48. Strive For Few Dependencies Can we make keep up with JS better? Your goal:
49. Evaluating Open Source libraries • Does it actually do what you need it to?
 Don’t eat soup with a shovel, don’t dig a ditch with a spoon. • What is the quality of code?
 Does it utilize modern best-practices? • Actively developed?
 Software is never “done.” • Active user base? • Documentation? • What dependencies does it rely on? Can we make keep up with JS better?
50. vs Can we make keep up with JS better?
51. Evaluating Open Source libraries • Does it actually do what you need it to?
 Don’t eat soup with a shovel, don’t dig a ditch with a spoon. • What is the quality of code?
 Does it utilize modern best-practices? • Actively developed?
 Software is never “done.” • Active user base? • Documentation? • What dependencies does it rely on? Can we make keep up with JS better?
52. Code should be written to minimize the time it takes for someone else to understand it. Can we make keep up with JS better? Write Readable Code.
53. We believe: • Write for another human being, don’t focus on micro-optimizations • Invest in modern JavaScript versions • Pack information into variable names • Commenting is to help the reader know as much as the writer.
 Don’t comment things that are already apparent by reading the code. • Embrace the language Can we make keep up with JS better? Write readable code.
54. JavaScript is a multi-paradigm language.
 It supports programming in different styles: • Procedural: (imperative), like C • Object-oriented: objects are primary building blocks, like Java • Functional: functions as first class citizens. Like Haskell, ClojureScript, or Elm. Can we make keep up with JS better? Write readable code.
55. Function Purity A function that relies only on its input arguments to derive the return value, and does not produce any side affects (such as modifying values or state outside of itself). Immutability Involves how you handle changes. Example: instead of adding items to an array, you create a new array with your item at the end of it. Can we make keep up with JS better? Write readable code.
56. Don’t try to be an “expert” in everything. Pick your tools wisely and then become expert in those. Focus on keeping up with the innovation within your sphere. Can we make keep up with JS better?
57. Can we make keep up with JS better? GraphQL Service Apollo Databases Microservices External APIs MOBILE WEB React React Native
58. How? Can? Why? Why JavaScript
 can be is great.
59. Why JS can be is great. Less, but better WE BELIEVE
60. Optimized for product teams JAVASCRIPT IS Why JS can be is great.
61. Why JS can be is great.
62. Node proved to be 2-5 times faster… “ “ - Kiran Prasad Our Node code base [is] 1,000 to 2,000 lines of code. The Ruby code base [was] 60,000. “ “ On ’s move to Node.js from Ruby on Rails Why JS can be is great.
63. Other Product Teams using Node.js Why JS can be is great.
64. Build for change WE BELIEVE Why JS can be is great.
65. Easy Performant Well known Ubiquitous JavaScript Why JS can be is great.
66. Every company is a software company WE BELIEVE Why JS can be is great.
67. IN SHORT, SOFTWARE IS EATING THE WORLD. M A R C A N D R E E S E N (he made )
68. IN SHORT, SOFTWARE IS EATING THE WORLD. M A R C A N D R E E S E N (he made ) JAVASCRIPT IS EATING SOFTWARE.
69. Q&A David Woody Conrad VanLandingham @davidjwoody @conrad-vanl #makeJSga Thank you!