JSConf.ar 2014 | Final Thoughts

so now we're going to the Q&A with andreas and Brendan we have five questions selected from your tweets so please take a seat here this is so exciting I'm so close to him I have a phablet loaded with questions

so the first one came from a tweet that's I think it's really really interesting so Brandon at what point did you start imagining that JavaScript could one day run and in control robots or games within games or zombies in WebGL compiled from C++ when I think around the time friends went off the air and I lost my gig there that's Chandler

uh no III didn't foresee all that I I thought it was going to be a glue language or what some people call duct tape language which is really I think not not a meaningful phrase it was going to be the little you know brother or the sidekick to Java and Java will do all the applets and components and beans and those would be in your browser and JavaScript would just be how you glued them together sort of like visual basic was to C++ in Microsoft's Windows

environment at the time but John never really got out of the applet cage it never loaded quickly it never learned about the Dom so I think that that was fatal awesome so basically jealousy was only going to be for embedding applets now it's for reinventing the JVM inside JavaScript it's pretty awesome so another thing that comes up a lot is JavaScript to some people has good parts and bad parts and now with old es mi

administered six and seven innovations and additions it creates new opportunities for now narrowing down again do you foresee that we are going to be creating JavaScript a good parts again now that we get all these new features I think this is true of the web in general like HTML has bad parts CSS I think we all know has bad parts the funny thing is people think when you have an evolving system that if a new

requirement comes into the system you have to evolve quickly that's not how it works in nature you are have to have had the genetic diversity and already have evolved to survive the new disease or the new predator so the same with javascript and HTML and CSS they're going to have too much in them they're going to have mistakes they're going to have things that you can't remove because they already are used by some pages their apps on the web but they can be deprecated and they can fade away and so I you know I just tweeted

back earlier before coming on stage I don't agree with Crockford he's too prescriptive astir my taste he says you know they're the bad parts you must never use and there are these little good parts that I say you should use like the closure pattern against the prototypal pattern it's too it's too extreme and JavaScript needed to have more patterns or more strength to it in order to survive for unforeseen circumstances and needs to keep evolving as it has so I I think there will

continue to be messy evolution with bad parts and we won't even know they're bad until later that's the that's the killer don't you wanted is it off here's no opinion can we hello yeah all right all right yeah I think it's especially the part around removing things being difficult is ray true um Brennan's explanation reminded me of a property I