(public).sospep.subjects ~ view article ~ state-of-javascript-2016-survey

<h1 style="text-align: center;">state of javascript - 2016 survey</h1>
<h2>[WHAT]</h2>
<ol>
<li>&nbsp;] by Sacha Greif @stateofjs.com - survey of 9000+ developers on the javascript, broken down into language versions(flavors), front end frameworks, state management, api layers, full stack frameworks, testing frameworks, css tools, build tools, mobile frameworks, features, opinions, developer profiles, conclusions.&nbsp;</li>
</ol>
<h2>[WHY]</h2>
<ol>
<li>] where developers stand on the javascript ecosystem, circa 2016,&nbsp;</li>
<li>] broken down into categories</li>
<li>]&nbsp;</li>
</ol>
<h2>[WHERE]</h2>
<ol>
<li><strong>] READ THE FULL ARTICLE</strong></li>
<ol>
<li>]&nbsp;<a href="http://stateofjs.com/" target="_blank">The State of JavaScript &ndash; Survey results</a>&nbsp;(stateofjs.com)</li>
</ol></ol>
<h2>[WHEN]</h2>
<ol>
<li>] 2016-10-08 &nbsp;</li>
</ol>
<h2>[EXAMPLE]</h2>
<ol>
<li><strong>] <a href="http://stateofjs.com/2016/introduction/" target="_blank">introduction</a></strong></li>
<ol>
<li>] # # &nbsp;JavaScript is either turning into a modern, reliable language, or a bloated,&nbsp;<a href="https://twitter.com/thomasfuchs/status/708675139253174273" target="_blank">overly complex dependency hell</a>. Or maybe both?</li>
<li>] What's more, there's just&nbsp;so many&nbsp;options: Do you use React or Angular 2? Do you really need Webpack? And what's this month's recommended way of dealing with CSS?</li>
<li>] wasnt sure, so I created a survey, survey says ...</li>
</ol>
<li><strong>] <a href="http://stateofjs.com/2016/flavors/" target="_blank">javascript flavors</a> ( aka versions)</strong></li>
<ol>
<li>] ES6 is the new standard</li>
<li>] CoffeeScript is past its time.&nbsp;</li>
<li>] a new wave of flavors is coming</li>
</ol>
<li><strong>] <a href="http://stateofjs.com/2016/frontend/" target="_blank">front end frameworks</a></strong></li>
<ol>
<li>] you cant go wrong with React</li>
<li>] vuejs is the new up and comer</li>
<li>] Angular2 &gt; Angular</li>
</ol>
<li><strong>] <a href="http://stateofjs.com/2016/statemanagement/" target="_blank">state management</a>&nbsp;</strong></li>
<ol>
<li>] redux is the top dog</li>
<li>] this is still in a state of flux&nbsp;</li>
</ol>
<li><strong>] <a href="http://stateofjs.com/2016/api/" target="_blank">API layers</a></strong></li>
<ol>
<li>] GraphQL looks promising</li>
<li>] REST apis are still the standard by a large margin&nbsp;</li>
</ol>
<li><strong>] <a href="http://stateofjs.com/2016/fullstack/" target="_blank">full stack frameworks</a></strong></li>
<ol>
<li>] this category dominated by MEAN and METEOR</li>
<li>] the "all in one" isnt that popular&nbsp;</li>
</ol>
<li><strong>] <a href="http://stateofjs.com/2016/testing/" target="_blank">testing frameworks</a></strong></li>
<ol>
<li>] Mocha and Jasmine lead the pack.</li>
<li>] Overall, developers are not happy about JavaScript testing.</li>
</ol>
<li><strong>] <a href="http://stateofjs.com/2016/css/" target="_blank">CSS tools</a></strong></li>
<ol>
<li>] SASS/SCSS is the dominant framework.</li>
<li>] CSS Modules are probably worth looking into as well.</li>
</ol>
<li><strong>] <a href="http://stateofjs.com/2016/buildtools/" target="_blank">build tools</a></strong></li>
<ol>
<li>] Webpack and Gulp are the shiny future.</li>
<li>] Grunt may become a thing of the past (with all but a grunt)</li>
</ol>
<li><strong>] <a href="http://stateofjs.com/2016/mobile/" target="_blank">mobile frameworks</a></strong></li>
<ol>
<li>] Native apps are still the most common solution.</li>
<li>] React Native is showing promise.</li>
</ol>
<li><strong>] <a href="http://stateofjs.com/2016/features/" target="_blank">features</a>&nbsp;</strong></li>
<ol>
<li>] server side rendering&nbsp;</li>
<li>] code splitting</li>
<li>] optimistic updates</li>
<li>] hot module reloading</li>
<li>] time travel debugging</li>
<li>] real time operations</li>
<li>] dead code elimination</li>
<li>] progressive enhancement&nbsp;</li>
<li>] other features = offline usage, service workers, static type system, accessability, isomorphic architecture,&nbsp;</li>
</ol>
<li><strong>] <a href="http://stateofjs.com/2016/opinions/" target="_blank">opinions</a>&nbsp;</strong></li>
<ol>
<li>] building javascript apps is overly complex right now - agreed 59%</li>
<li>] javascript is over used online - disagreed 51%</li>
<li>] javascript ecosystem is changing too fast - agreed 58%</li>
<li>] i would like javascript to be my main programming language - agreed 66%</li>
<li>] javascript is moving in the right direction - agreed 78%</li>
<li>] i enjoy building javascript apps - agreed 82%</li>
<li>] this survey is too damn long - agreed 47%&nbsp;</li>
</ol>
<li><strong>] <a href="http://stateofjs.com/2016/profiles/" target="_blank">developer profiles</a></strong></li>
<ol>
<li>] experience 2-5 years 29%, 5-10 years 30%</li>
<li>] salary 50-100k 38%, 100 -200k 25%</li>
<li>] favorite text editor - sublime, atom, webstorm, vim, vs code, emacs,&nbsp;</li>
</ol>
<li><strong>] <a href="http://stateofjs.com/2016/conclusion/" target="_blank">conclusion</a>&nbsp;&nbsp;</strong></li>
<ol>
<li>] Some technologies turned out to be clear winners (React), some emerged as promising up-and-comers (Vue), and some proved to be on their way out (CoffeeScript).</li>
<li>] At the same time, things get murkier when it comes to areas such as testing, state management, or the API layer. Will Redux be able to maintain its (relative) dominance? Will GraphQL fulfill its destiny and end up replacing REST? Will we finally find a way to test JavaScript apps we can all agree on?&nbsp;</li>
<li>] If I had to draw a single conclusion from all this though, it would be that the future looks bright for JavaScript. Sure, the churn rate is high, but on the other hand each successive generation of libraries is making huge leaps in terms of maintainability and developer experience. So it's fine if the road is a little bumpy at times, because I'm pretty sure it goes in the right direction. &ndash; Sacha Greif</li>
</ol></ol>
<h2>[HOW-TO]</h2>
<ol>
<li>]</li>
</ol>
<h2>[REFERENCE]</h2>
<ol>
<li>] SRC = best-of-<a href="https://news.ycombinator.com" target="_blank">Hacker-News-2016-10-03</a>,&nbsp;544 <a href="https://news.ycombinator.com/item?id=12627693" target="_blank">comments</a>&nbsp;(346)&nbsp;</li>
</ol>
<h2>[RELATED]</h2>
<div><ol>
<li>] # 5297 -&nbsp;<a id="5297" href="/view/article?id=5297&amp;startpage=0" target="_blank">How-it-feels-to-learn-javascript-in-2016</a>,] by Jose Aguinaga @hackernoon.com - Jose explores the state of whats current in the world of javascript development</li>
<li>] # 5296 -&nbsp;<a href="/view/article?id=5296" target="_blank">SUMMARY-reflections-of-an-old-programmer</a>&nbsp;- ] by Ben Northrop, @bennorthrop.com - Northrop explores his experience in the programming feild to other professions and how the knowledge he has learned needs to be continually discarded and replaced with the "new and innovative" tools of the day,</li>
<li>] # 5025 -&nbsp;<a id="5025" href="/view/article?id=5025&amp;startpage=0" target="_blank">javascript-state-of-the-art-2016</a>&nbsp;- ] by Francois Ward @medium.com - Ward's personal picks for most pieces of a modern web application. Some choices are likely controversial and I will only give basic reasoning behind each choices.</li>
<li>+] # # - summary javascript 2016 (es-2016) - highlights / changes</li>
<li>] # 1663 - <a href="/view/article?id=1663" target="_blank">BOOK javascript</a>&nbsp;- &nbsp;my collection of javascript articles, notes, examples and more</li>
</ol></div>
<h1 style="text-align: center;">&nbsp;</h1>

~ view article ~ Chapter] ch-099-index FROM [ Book] language-javascript IN [ libraries] technology-developer-www