1. Exquisite Tweets from @nolancaudill, @bertrandom, @dokas, @cjmartin, @rort, @heyjoshua

    blechCollected by blech

    I wonder what drove the *explosion* of JS tools such as backbone and coffeescript: better browsers, better engineers, or a tangled mix?

    Reply Retweet Like

    nolancaudill

    Nolan Caudill

  2. @nolancaudill I'm pretty sure coffee script was invented during a session involving a train set, mutual touching, and imitation crab meat.

    Reply Retweet Like

    bertrandom

    Bertrand Fan

    @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…

    Reply Retweet Like

    bertrandom

    Bertrand Fan

  3. Missing tweet: 156794276464955392

  4. @waferbaby @nolancaudill Event-driven programming is useful in most systems and I never got good at twisted. Javascript I can handle.

    Reply Retweet Like

    bertrandom

    Bertrand Fan

  5. Protected tweet: 156795426970939393
    You might be able to see it if you sign in with Twitter.

  6. @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?

    Reply Retweet Like

    nolancaudill

    Nolan Caudill

  7. @nolancaudill @ysaw Technically dojo had templates (django-esque) and MVC through dijit way before but no one took the time to learn it

    Reply Retweet Like

    bertrandom

    Bertrand Fan

  8. @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.

    Reply Retweet Like

    nolancaudill

    Nolan Caudill

  9. Protected tweet: 156798570782146562
    You might be able to see it if you sign in with Twitter.

  10. @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.

    Reply Retweet Like

    bertrandom

    Bertrand Fan

  11. Protected tweet: 156800331601285120
    You might be able to see it if you sign in with Twitter.

  12. @hartsell Architecture-as-amusement: an interesting design pattern. So you think a lot of the new stuff is "just because we can"?

    Reply Retweet Like

    nolancaudill

    Nolan Caudill

  13. @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.

    Reply Retweet Like

    dokas

    Phil Dokas

    @nolancaudill Another interesting thing is that CS/Backbone/_ are all from the same man (originally). There's clout with that, plus…

    Reply Retweet Like

    dokas

    Phil Dokas

  14. @bertrandom "It currently takes about 40 seconds to run print(1+1)." Blazing Fast!

    Reply Retweet Like

    cjmartin

    Chris Martin

  15. Protected tweet: 156804250586984448
    You might be able to see it if you sign in with Twitter.

  16. @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.

    Reply Retweet Like

    nolancaudill

    Nolan Caudill

    @dokas @ysaw Absolutely agree. I love JS but before node, your main option server-side was rhino with all its JVM excess.

    Reply Retweet Like

    nolancaudill

    Nolan Caudill

  17. @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.

    Reply Retweet Like

    rort

    rort

  18. @rort @nolancaudill @dokas @ysaw Oh god yes. Especially now that dtrace can give you full on stack traces for profiling in VM code.

    Reply Retweet Like

    heyjoshua

    Joshua Cohen