Enough with the JavaScript already
fr.slideshare.net
Enough with the JavaScript already
1–10 of 231 posts
Re: Enough with the JavaScript already
#2[deleted]
Re: Enough with the JavaScript already
#3[deleted]
This was clearly a talk you were supposed to watch, not attempt to read the slide deck through later. Many of my talks are like that, and to avoid people complaining online "your slides suck" even though the people at the talk usually were in agreement that "that was an amazing talk", I always go out of my way to use presentation technologies that are as random and esoteric as possible to make certain that when I am asked "can we have a copy of your slides" the answer is "I guess, but it will be really hard and of no use to you".
Re: Enough with the JavaScript already
#4[deleted]
Nicholas Zakas is a famous JS dev that worked at Yahoo. And the slides have nothing to do with a rant against JS , if it is why you hate them.That's the context.
Re: Enough with the JavaScript already
#5Slide 19 seems broken for me.
I remember from last time someone posted this that slide 19 was like slide 18 but with all of the features over in the JS box. In this version, both slides are identical.
Re: Enough with the JavaScript already
#6Though I would like to see the talk in its fullness, and I am a full-on Javascript fanboy, I have to agree with the core thesis. In 99% of cases, there's no reason to do all rendering client-side, especially on content-centric sites. And devs do sometimes get too dependent on kitchen-sink libraries, rather than rolling their own native JS to address their own specific need.
Re: Enough with the JavaScript already
#7Why store state in DOM? Isn't that bad practice?
I remember reading DOM access is the slowest part of JS [needs verification]. So you want to trade performance for few dozen kilobytes of assets that can be cached?
Re: Enough with the JavaScript already
#8Who's the superman?
Re: Enough with the JavaScript already
#9[deleted]
Martin Fowler refuses to publish the slides of his talks because they only make sense in the context of his talks. Seems to be a good decision.
Re: Enough with the JavaScript already
#10Why store state in DOM? Isn't that bad practice? I remember reading DOM access is the slowest part of JS [needs verification]. So you want to trade performance for few dozen kilobytes of assets that can be cached?
Because then you can create a fallback if Javascript isn't enabled - use a server side language to manipulate the DOM on page load to give the same state as if the Javascript were there