Best of Fluent 2012: Maintainable JavaScript
HTML-код
- Опубликовано: 7 авг 2024
- Video of Nicholas Zakas from his Fluent Conference 2012 Presentation
Maintainable JavaScript tackles the difficult problem of writing code as part of a large team. When you're writing code that only you will change, there aren't any issues. As soon as you're writing code that someone else is going to also be changing, you need to think harder about the decisions you make. Will another developer be able to understand what you did? Did you organize your code in such a way that it's easy to adapt and extend? Long after you're gone, will others be able to continue using the same code, or will it need to be rewritten because no one understands it? This session shows the best practices used by teams to ensure their JavaScript is as maintainable as possible.
NOTE: To view an HD version go to: • Best of Fluent 2012: M...
About Nicholas Zakas
Nicholas C. Zakas worked at Yahoo! for almost five years, building and defining front-end strategy for some of Yahoo's largest sites. Nicholas is also the author of several books, including High Performance JavaScript, Professional JavaScript for Web Developers, and Professional Ajax.
Don't miss an upload! Subscribe! goo.gl/szEauh
Stay Connected to O'Reilly Media by Email - goo.gl/YZSWbO
Follow O'Reilly Media:
plus.google.com/+oreillymedia
/ oreilly
/ oreillymedia 
Наука
I too like Nicholas Zakas, both his writing and speaking. No pun intended, but I find his speech very fluent, and the combination with his profound knowledge makes it awesome.
Interesting enough to stick to till the end,
resourceful enough to take away some great tips.
Keeping HTML markup separate from JavaScript is contrary to the today's component era (ReactJS particularly), which is basically mixing JavaScript and HTML (JSX)
did he said IE when he coughed? :p one of the few videos I re-watch frequently. This man is awesome.
Anam Ahmed he did say IE when he coughed :D
Awesome talk. Tools are not as up-to-date anymore, but generally awesome.
This is a great talk, I always share it and reference in my own presentations.
very useful stuffs. thanks, nicholas.
Very Userful Talk.
Great video. Very helpful. Thanks :)
Try to maintain the size of your Javascript to zero bytes. It's the best choice unless you want popups on your site, you don't need and/or want it.
Thats one thing that makes Java and class based languages better than Javascript. If someone overrides a method in Javascript it can take days to figure out the bug. However in Java its only a matter of seconds to find incompatible overrides due to compile time checking.
So simple. Thanks dude!
Great great talk, witty funny. Thx.
don't be afraid of long names and name things logicaly: AbstractSingletonProxyFactoryBean
I'd just like to state for the record that "Id" is not an acronym, its an abbreviation. It means "Identification" or "Identifier", not like "I-Dentifier". So capitalizing both letters would be incorrect.
I once had a 45 minute argument about whether or not JSLINT errors should break our jenkins build. Though the style itself doesn't effect the program, it was a good way to enforce our style guide. Any thoughts?
I assume you're referring to the fact that Pi is all caps? All of the Math constants are capitalized, following the general practice of capitalizing constants (the slide following camel casing).
/watch?v=nZihjH6_Qns
I have no idea why they uploaded it twice but this one has 720p
The slides: slideshare. net/nzakas/maintainable-javascript-2012
I am new to Javascript coding and thought this was a great video!
I have a question though.
At 30:00 it says to keep css style out of Javascript. How would one manipulate the css style of an html element then?
Example code:
jsfiddle.net/5Ba2u/
How would the above be done for better coding practice?
Thanks in advanced.
There's a HD version in the description, no?
24:00, what about Math.PI ?
getElementById & innerHTML is not JavaScript but DOM API !
Wow, the only expletive I heard was "Internet Explorer"
Add a CSS class instead - that's what they're for, updated your jsFiddle: jsfiddle.net/5Ba2u/3/
Use class name to change the style;
15:50
Just because JavaScript is classless, doesn't mean you have to be ))))
fck classes use functions
Hey RO2player, why don't you join the rest of us in the wonderful world of 'check the description for the HD link' before posting a comment that already has been addressed? Go on, try it, you might like it.
He looks like Steve Jobs, junger JavaScript genious!
Hey Oreilly Media, why don't you join the rest of the us in the wonderful world of 'at least' 720p? Go on, try it, you might like it.
lol "Knuth is my homeboy"
Great talk, could have done without all the expletives, had ask my four year old leave the room.
Harshed word I heard was crap and I don't view that as an expletive. I do however view IE as an expletive if it refers to any version before 10.
Wow! "Just because JavaScript is classless you don't become". :-)
LOL, 9:25 "Debuggable... which is not a real word... btw... According to M$ word anyway." I can't tell if he was telling a joke there or not.
Tomás Martínez check this out xD 28:10 me recordó a ti xD
???.... porque?
Tu buscando bugs en javascript, no? si viste el minuto que te dije? xD
The XMLHttpRequest name feels wrong no matter how you write it.
Xml? Who capitalizes Xml? Ok, all caps then, like in the wild
But how about the Http part then? If we put it all caps the reader will lookup for the new XMLHTTP protocol. We need to separate it somehow. Underscore? Well yes, but we use underscore for separating words in variable names.
There is absolutely no way to win this. Only by completely changing the object name. But how could you name the object of an XML HTTP request? ARGH!
There was a rule used for a while that abbreviations are capitalised until 3 and after that only the first letter is capitalised. I guess Http is more acceptable than Xml.
The whole point of camel casing is to emphasise word boundaries. You can see that XML and Http are separate words because 'H' must be the first letter in a word. Of course this is totally dependant on luck, because een XML NTP request would be XMLNTPRequest.
It's now widely the norm to just capitalise the first letter: XmlHttpRequest. Maybe it feels crappy to capitalise one letter, but at least it serves its purpose consistenly.
Κώστας Λουπασάκης There is a way to win this :) => ExtensibleMarkupLanguageHyperTextTransferProtocolRequest
My bet is that it was a joke ...