Mde txjs 2011_full-stack_fallacies
Download as KEY, PDF0 likes671 views
With the mainstreaming of server-side JavaScript, the possibility of full-stack JavaScript development finally seems to be coming to fruition. Writing once, and running the same code everywhere seems like the obvious big win, along with the ease of writing complex server-side applications in a simple, flexible language like JavaScript. Actually, full-stack JS is awesome, but these aren't necessarily the reasons why. This talk will bust some of the myths about full-stack JS development, and take a realistic look at the benefits of 'JS everywhere.'
1 of 13
Downloaded 10 times
Mde txjs 2011_full-stack_fallacies
- 1. Full-Stack JS Fallacies Matthew Eernisse TXJS 2011
- 2. Who am I? Matthew Eernisse @mde on Twitter Work at Yammer
- 4. • Shared MVC? • DOM vs. DB • Plain JS, fancy JS
- 5. Fallacy: JavaScript is simple
- 6. • SSJS is JavaScript, JavaScript is simple • Async is hard • Slippery slope problem
- 7. Win: zero context- switch
- 8. • “Can I ask you a quick question?” • Staying in the Zone • Why do we program?
- 9. Win: client-side coders moving to server
- 10. • Front-end JS coders don’t know the server • Low-level server coders don’t know JS • Fun ensues
- 11. Win: server JS is a lingua franca
- 12. • “I hate JavaScript” • JS idiom is very flexible • Uniquely pragmatic focus
- 13. Matthew Eernisse http://twitter.com/mde https://github.com/mde Yammer Developer Center http://developer.yammer.com/