I wonder what drove the *explosion* of JS tools such as backbone and coffeescript: better browsers, better engineers, or a tangled mix?
4:47pm Jan 10th 2012 via web
@nolancaudill I'm pretty sure coffee script was invented during a session involving a train set, mutual touching, and imitation crab meat.
5:29pm Jan 10th 2012 via Twitter for Mac in reply to nolancaudill
@nolancaudill node.js on the other hand has been a game-changer for me. I just wish I knew enough C to fix v8-profiler github.com/dannycoates/v8…
5:44pm Jan 10th 2012 via Twitter for Mac in reply to nolancaudill
@bertrandom @nolancaudill: Game-changer howso?
5:47pm Jan 10th 2012 via Twitterrific for Mac in reply to bertrandom
5:49pm Jan 10th 2012 via Twitter for Mac in reply to waferbaby
5:51pm Jan 10th 2012 via web in reply to nolancaudill
@ysaw So a better JS engine let us do more things - I buy that. But is the shift of templates and MVC stuff to JS also a result of that?
5:59pm Jan 10th 2012 via web in reply to ysaw
@nolancaudill @ysaw Technically dojo had templates (django-esque) and MVC through dijit way before but no one took the time to learn it
6:01pm Jan 10th 2012 via Twitter for Mac in reply to nolancaudill
@bertrandom @ysaw I remember dojo not-so-fondly. I know it got better, but it was not fun in anyway to work with at the time.
6:02pm Jan 10th 2012 via web in reply to bertrandom
@nolancaudill JS used to be too slow to do templates anyway, it really comes down to speed I think, and the rest progressed naturally.
6:04pm Jan 10th 2012 via web in reply to nolancaudill
@nolancaudill Yeah, dojo only got good when they went from 0.4 -> 0.9, much like YUI2 -> YUI3. I wish jquery hadn't won out of simplicity.
6:10pm Jan 10th 2012 via Twitter for Mac in reply to nolancaudill
@hartsell Architecture-as-amusement: an interesting design pattern. So you think a lot of the new stuff is "just because we can"?
6:13pm Jan 10th 2012 via web in reply to hartsell
@nolancaudill @hartsell Do you need any more proof than this? github.com/jterrace/js.js
6:14pm Jan 10th 2012 via Twitter for Mac in reply to nolancaudill
@nolancaudill @ysaw I’d argue that part of it is that node enticed a new group of developers to consider JS and they brought preferences.
6:20pm Jan 10th 2012 via Twitter for Mac in reply to nolancaudill
@nolancaudill Another interesting thing is that CS/Backbone/_ are all from the same man (originally). There's clout with that, plus…
6:22pm Jan 10th 2012 via Twitter for Mac in reply to nolancaudill
@bertrandom "It currently takes about 40 seconds to run print(1+1)." Blazing Fast!
6:25pm Jan 10th 2012 via Twitter for Mac in reply to bertrandom
@cjmartin @bertrandom that is some high quality wankery there
6:27pm Jan 10th 2012 via Twitter for Mac in reply to cjmartin
@dokas On my surveying of stuff last night, the same 2-3 names kept popping up, reminded me a bit of Rails coming on back in the day.
6:36pm Jan 10th 2012 via web in reply to dokas
@dokas @ysaw Absolutely agree. I love JS but before node, your main option server-side was rhino with all its JVM excess.
6:37pm Jan 10th 2012 via web in reply to dokas
@nolancaudill @dokas @ysaw ugh rhino. @chyekk and I worked on a rhino based js app server in '06.. I'll take node any day over it.
11:02pm Jan 10th 2012 via Twitter for iPhone in reply to nolancaudill
@rort @nolancaudill @dokas @ysaw Oh god yes. Especially now that dtrace can give you full on stack traces for profiling in VM code.
11:15pm Jan 10th 2012 via web in reply to rort
Connect with Twitter
A website by @jwheare