(public).sospep.subjects ~ view article ~ REVIEW-podcast-hanselminutes-383

<h1 style="text-align: center;">hanselminutes #383</h1>
<ol>
<li>] LJ - hanselminutes podcast# 383 - enough of javascript already</li>
<ol>
<li>] discussion on front end web development and the smarter use of javascript. he advocates that developers use fewer libraries and write smarter JS. Where do we start? What are the four opportunities to load JavaScript? Is Progressive Enhancement still the right solution? Aren't we supposed to be writing MORE JavaScript? Nicholas educates Scott on all the right moves when writing front ends on today's web.</li>
<li>] MISTAKE - using JS to render all the html for the entire page,&nbsp;</li>
<ol>
<li>] use JS to manipulate elements on page once it has been fully loaded&nbsp;</li>
</ol>
<li>] first load</li>
<ol>
<li>] &nbsp;</li>
</ol>
<li>] 1000+ js libraries</li>
<ol>
<li>]&nbsp;</li>
</ol>
<li>] there is no 1 write way to do things</li>
<ol>
<li>]&nbsp;</li>
</ol>
<li>] web is going in cycles,&nbsp;</li>
<ol>
<li>] flash was IT, then b/c of the size of the binary downloads, ... - devs moved away from it &nbsp;</li>
<li>] but now web app's JS files(dloads) are getting so large that its impacting site performance(especially on mobile)&nbsp;</li>
</ol>
<li>] avoiding duplication of writing SAME js for server and client</li>
<li>] you dont need to do everything ins JS , if it's possible to do something in HTML, do it in HTML</li>
<ol>
<li>] if its possible in CSS do it in CSS</li>
<li>] if its possible in SERVER, do it in</li>
<li>] if its NOT possible on the above, then do it in JS</li>
</ol>
<li>] example client side functionality for, dont go back to server to 'sort' a long list for example,&nbsp;</li>
<ol>
<li>] sorting -</li>
<li>] searching withing results -</li>
<li>] type ahead - ?&nbsp;</li>
<li>] ...</li>
</ol>
<li>] JS libraries&nbsp;</li>
<ol>
<li>] many developers fall into trap of "whats the best library" to do this,&nbsp;instead of whats the 'best way' to do this</li>
<li>] with libs like jq and jq plugin's its easy to do this... just google 'desired functionality', and then add/yet another js plugin&nbsp;</li>
<li>] prb with libs like jquery and backbone is that the abstraction leads to devs not understanding the JS&nbsp;</li>
</ol>
<li>] it's good to know what JS is doing under the hood</li>
<ol>
<li>] instead of automatically doing stuff with library try to do stuff in pure js, maybe you dont even need a library,&nbsp;</li>
<li>] this will also help to give you a better understanding of js</li>
</ol>
<li>] there are four(4) JS load times, yep, theres 4 ?, when to load the 'particlular js' , what do you need, when do you need it</li>
<ol>
<li>] head tag ( minimal, don't put a lot of js in here, )</li>
<li>] before closing body tag - (browser can render page content while js is loading, user is not 'waiting' whilst looking at a blank page)</li>
<li>] after window.onload() - secondary or tertiary action ( something a user 'might' do on page, ex 'search' when viewing a product page &nbsp; )</li>
<li>] on demand - use (any)trigger to load in js for a particular function, you need to know what functionality users of a site are using,&nbsp;</li>
</ol>
<li>] people arent using metadata enough, use HTML attributes to carry state data VS using js&nbsp;</li>
<ol>
<li>] can use metadata to set state, then use JS to monitor/change</li>
<li>] element attribute(s)&nbsp;</li>
<li>] js widgets mimic / track element by creating SHADOW DOM</li>
<li>x] let html do some of the heavy lifting,&nbsp;</li>
<li>] the DOM is essentially a data structure,&nbsp;</li>
<li>] qrying the DOM to get values is not expensive</li>
<li>] touching the DOM , concerns about the (performance) cost of = , ex&nbsp;</li>
</ol>
<li>] ex github -&nbsp;pg view / repo</li>
<ol>
<li>] using html5 pushstate and pop state to reload parts of pages that dont change, vs pulling down the whole page</li>
</ol>
<li>] VIDEO - talk&nbsp;</li>
</ol></ol>
<iframe src="http://www.youtube.com/embed/li4Y0E_x8zE" frameborder="0" width="560" height="315"></iframe>
&nbsp;
<h1 style="text-align: center;">Enough with the Javascript already</h1>
<ol>
<li>] dark chocolate covered almonds are fantastic</li>
<ol>
<li>] they are great, but we dont want them all the time and everywhere we go ..&nbsp;</li>
</ol>
<li>] web apps are comrised of primarily</li>
<ol>
<li>] server side -&nbsp;</li>
<li>] html -&nbsp;</li>
<li>] css -&nbsp;</li>
<li>] js -&nbsp;</li>
</ol>
<li>] trend is that developers are moving everything to ..</li>
<ol>
<li>] JS&nbsp;</li>
<li>] JS is the most difficult and time consuming(&amp;expensive) to maintain, makes sense to use less of it&nbsp;</li>
</ol>
<li>] example - popular sites</li>
<ol>
<li>] avg = 187kb gzipped js - approx 600 kb unzipped</li>
</ol>
<li>] progressive enhanement still works</li>
<ol>
<li>] serve up html</li>
<li>] add js to manipulate the &nbsp;</li>
</ol>
<li>] 4x to load JS</li>
<ol>
<li>] head -&nbsp;</li>
</ol></ol>

~ view article ~ Chapter] hanselminutes FROM [ Book] sources-technology IN [ libraries] technology