© 2017 Progress. All Rights Reserved. - 2016 And Beyond And 2016 - The Future of JavaScript Interviews with Developers JavaScript Building the of Tomorrow WHITEPAPER © 2017 Progress. All Rights Reserved. Table Contents of jQuery jQuery 16 / Mass Critical / 21 / Aurelia What will the be most used feature in 2016, from ES 2015? Which feature added in 2015 will considered be the most critical in 2016? /5 ECMAScript 2016 (ES7) /4 Libraries and Frameworks Frameworks Libraries and 14 / Frameworks AngularJS Will JavaScript continue to rise in use? What issues will remain in 2016 that future updates to JavaScript will need to resolve? 11 / Will one JavaScript package manager rise, destroying all others? /10 What will the be most important proposal finalized in 2016 and released in ES 2017? React React In 2016, which feature from ES 2015 will developers wish hadn't been added? Will run times fully support ES2015 by the end of 2016? /8 Will JS to JS transpilers thrive in 2016? /7 / / 18 / 16 20 / 14 / 13 / 6 / 8 / 9 © 2017 Progress. All Rights Reserved. Final developer predictions 29 / 28 Polymer / JavaScript’s new frontiers in 2016 apps /37 Desktop Native /35 apps mobile Meteor Meteor Progress Kendo UI Node.js JavaScript’s New Frontiers Ember Ember PhoneGap and Cordova Web Components / / / 24 25 32 / / 26 23 / 33 / 38 / 30 © 2017 Progress. All Rights Reserved. questions. and the thoughts of those who answered my mixture of answers, containing both my thoughts follows is asummary of the questions asked with a more than just my own personal thoughts. What couple of questions to springboard this article with future, Ipolled the JavaScript community with a In order to make areasonable prediction about the 2016. into forward JavaScript language, and the community, as we look predictions about what might happen with the going to talk about the future and make afew today. Hooray, right! This is old news. Instead, I'm already happened or how we got to where we are In this article, Iam not going talk about what has span and success of JavaScript. life creation, JavaScript the historical details about most readers have already heard, ad nauseam, the not saying anything surprising here. In fact, Iassume and the fact that it world is the eating evolution JavaScript of areyou likely the familiar with development (even non-web dev) in recent years, If you have had anything to do with software (ES7) 2016 ECMAScript
Contents . Iguess I'm 4 @dfernandeza, github:spaced, @assaf, @BrianDukes @assaf, github:spaced, @dfernandeza, @alexbrbr,@codekult, @christosmatskas, @dfkaye, Chernov, @briankardell, Alex, @rlsix, Brendan, runspired, Nicholas Zakas, C. getify, js_dev, hemanth, sergiopereira, Kelly, Kitson Zackargyle, bahmutov, @ @softwarefloyd, rodneyrehm, @aortiz, You are: several topics. My thoughts were challenged and enlightened on my questionnaire about the future of JavaScript. Many thanks to those who took the time to answer © 2017 Progress. All Rights Reserved. on in astrained and unbalanced position. that many non-Node developers have been sitting is like adding that fourth leg to athree-legged chair returned promise, but the addition of native modules usage of an arrow function or the simplicity of a Modules might not blow your hair back like aconcise language. to the addition vital well. According to @codekult behind modules were considered avital addition as critical addition, but afew did not. Promises right questionnaire agreed that modules were the most to actually realize it. Most of the participants in my native support, it might take all of 2016 for developers added to the language. course, Of due to its lack of modules consider abasic requirement. In 2016, I believe loading are, in fact, what most developers would languages. management Modules, dependency and but it is neither flashy or new to programming A native module system may new be to JavaScript, the most critical in 2016? considered be Which feature added will in 2015
Contents will deemed be the most important feature
, promises are the most 5 developer communities. until ES 2015 modules are flushed through the in aholding imports like HTML pattern things with even are vendors browserify. browser It would seem stop pretending with things like CommonJS and this materialize to some degree in 2016 so we can on both the client and the server. hoping I'm to see native single, a using of possibility system brings the browser in line with Node and the If you think about it, the addition of anative module webpack systemJS). or (e.g. babel) or atool that uses atranspiler (e.g. 2015 module syntax, you'll have to use atranspiler production is abit more complicated. To use ES However, making use of JavaScript modules in given that the concepts are similar to CommonJS Learning the new module syntax will easy, be @codekult worker and so on.” async functions, observables, fetch, service pairing for several other updates: generators, “Promises, because it is the base of the perfect , module syntax .
© 2017 Progress. All Rights Reserved. assert apet syntactical feature. Some say promises. Others say generators. Many and there does not seem to amass be consensus. been asking developers this question for over ayear which one will become the most used in 2016? I've allOf the features added to the language in 2015, feature in from 2016, 2015? ES What will bethe most used effect. massivea trickle-down Angular 2and Aurelia). Ibelieve this reality will have adopted by several popular front-end tools (e.g. 2016. This is mainly because the syntax is being syntax yet, Ibelieve they will most likely adopt it in If developers haven’t used the ES 2015 module ideal of tomorrow. systemJS will still the be stopgap used to deliver the realized. Thus, in 2016, solutions like webpack and the ideal is still many years away from being fully the past. In 2016, this will start to materialize, but systemJS) will an be unnecessary complexity from with the non-native loaders (browserify, webpack, module formats (e.g. commonJS, AMD, UMD) along syntax will work everywhere and the non-native One day, in the future, the native JavaScript module
Contents 6 ways of doing things. developers holding on very tightly to the CommonJS outbeen left entirely. In 2016, we'll see alot of course,Of some people think modules could have forward making it the most used as well. important feature, as Ijust asserted, thus moving make sense if, in fact, the module syntax is the most and close behind that will promises. be This would in 2015 used in 2016 will the be module syntax, I predict that the most used feature from the update JavaScript modules and move past CommonJS. But, eventually, Ibelieve most developers will accept @assaf like CommonJS.” simpler something could have“Modules out left been for © 2017 Progress. All Rights Reserved. did more than Babel @softwarefloyd JavaScript-to-JavaScript transpiler. like some, fact, In unanimously agreed that Babel is the best that almost everyone from the questionnaire JS to JS transpilers are here to stay and it seems 2016? Will to transpilers JS JS thrive in
@softwarefloyd instance, really to me.” seems icky transpiled target language. TypeScript, for between the source language and the when the system type is significantly different ES7 transpilers are great, but Iget nervous like“I transpilers to apoint. Ithink and ES6 Contents were even fearful of anything that . 7 should negate some of this thinking. the usage of ES 2015 features in npm modules In 2016, the nudging from tools using ES 2015 and wait for proper support, believing that ES5 is enough. who want don't to transpile code and would prefer to There does seem to asmall be faction of developers following reasons: code turning source to transpiler In 2016, Ithink you'll see more and more developers 3 1 2 to accept atranspilation step. and to use these tools you'll likely need features (e.g. Angular Aurelia, 2, etc...) New tools are making use of ES 2015 usage of newer ES 2015 features. step is atrivial addition in return for in place and adding in atranspilation A build step is more than likely already 2015 features without transpiling.) features2015 without developers using 5.x+ get alot of ES code. (Keep in mind that Node 2015 source code to ES 5production in 2016 they will have to transpiler ES language for browser code. To do this of the new features introduced in the Web developers will want to make use for the © 2017 Progress. All Rights Reserved. 2016, is the class syntax. contentious and Ibelieve will remain contentious into (badly) needed. The only exception here that seems the new additions to the language were mostly all developerthe generally community believes that Given the gap between ES5 and ES6, it would seem wish hadn't been added? developers will 2015 In which 2016, feature from ES polyfill turningbe to atranspiler in 2016 using aloader exact reason that large numbers of developers will supported due to the loader thebe feature that takes years to become widely feature from ES 2015, module syntax, will likely The thing to note here is that the most important land they before features experimental proposed supporting transpilers rate of change provided by modern browsers and opinion. Ibelieve this is due to the faster than normal of the people in the questionnaire had asimilar end of 2016 given the rate of change in 2015 Node might just reach 90% to 95% support by the hurdle loading between and two three years given the module Realistically complete ES 2015 support could take ES2015 by the end of 2016? Will run times fully support
Contents . . However, modern browsers and . . Of course,. Of this is the
. Most . 8 from both camps. both from well, everything will Goodsoftware ok. be will still result internal and state. And, encapsulation strict of terms in to think this way. Those who do will continue to think think developer like will continue don't who “OOP” an of aprogram with the same principles. In 2016, those Why? Because not everyone approaches the design Will this tug-of-war settled be in 2016? Absolutely not. other side, you have those who think classes are evil. have those who think classes are good and on the A kind of tug-of-war is at work here. Onone side, you will continue and these anti-class developers will In 2016, grumbles about the addition of class syntax class contentious? class a traditional OOP language are obvious. So, why is The benefits to those who come to JavaScript from it. So, what's the big deal? Take it or leave it, right? want who those for inheritance their with dealing simpler and clearer syntax for creating objects and cut code. Its inclusion and purpose is to provide a In other words, class syntax is mostly just short there. always been has that inheritance sugar over the top of the prototype-based syntax was added in 2015 and its just syntactical classesneed JavaScript does not have classes . You knew that, right. However, class . And, it doesn’t © 2017 Progress. All Rights Reserved. evolving the language yearly with slight changes. yearly with language the evolving In fact, from 2016 onward, TC39 is only planning on not bring the same scale of changes that 2015 did. The first thing you should notice is that ES 2016 will addedbe to the language next are: existence. of out itself Apparently, that proposal cooked too long and burnt Well, if you haven't heard, it won't Observables. be and released in 2017? ES 2016 in finalized proposal What will bethe most important debate normal like class syntax. Once JavaScript is adopted, the continue to rise in to part additions to the language In fact, Ipredict we'll see the usage of JavaScript just lead to amass migration to JavaScript in 2016. against them. But, again, the addition of it could audience (i.e. actual users) in order to mount acase those who abstain from classes will have acaptive providing class syntax, the JS hook can set be so value of adding it is obvious. In other words, by to the language, Iwould hope the gateway drug And consider that even if one stand can't its addition spot. the update from 2015, then we are in areally good JavaScript itself. If this is the only issue in 2016 with is aprincipled disagreement that is larger than update.perfect The addition of the class syntax those developing the language crafted an almost Mostly because Ithink this points to the fact that update in 2015, Ithink the outlook for 2016 is good. this is the most contentious of part the massive continue to lobby that it shouldn't used. be But, if • • • •
Contents Async FunctionsAsync SIMD.JS -SIMD APIs +polyfill Array.prototype.includes Exponentiation Operator s of course continue will To date the proposals likely .
to to 9 async functions and promises. and functions async predict that most people will learning be and using language. If any time is in left the coming year, I to get “ninja stupid” learning the additions made in 2015 and how not Most of 2016 for many developers will spent be Functions Async the is proposal critical Before the news that the With With imagine this will continue to debated be to adegree. this addition would the be most important. In 2016, I proposal would withdrawn, be many believed that Object.observe with so many changes to the out of the running, the next Object.observe .
© 2017 Progress. All Rights Reserved. the faster we can get on to the native solution. quicker we can burn the commonJS wagon down, syntax is the only logical path forward. Ibelieve the and browserify bandwagon. course, Of the native This is why many have jumped on the commonJS to construct the modules contained in the packages. would have to an be agreement on the syntax used single package manager is ideal, but if it were there module format for JavaScript. not I'm convinced a even possible, would first have to settle on asingle developer front-end and Node the developer, if I think asingle package manager servicing both build complex applications. don't developers who and lacking concern for alarge group of website like Bower things that everyone should just use npm developers front-end and Many developers. believe package manager that could service both Node ways, this is adebate over the viability of asingle single package manager for JavaScript. In some into 2016 (and likely into 2017) will that be of a A topic of discussion in 2015 that will bleed over others? all manager rise, destroying JavaScriptWill one package
Contents . Ifind the perspective very narrow and abandon
10 convinced them to only use npm. duplicationthe that developers have suggested from both if you need too. This alleviates some of win? Isay, cares?” “Who -just use jspm.io and pull to whatever is to come. So will npm win or will bower literally sit on top of this issue and future be friendly for JavaScript package managers and jspm.io can because think Idon't we know what the future holds GitHub and even bower (with plugin). Ifavor jspm.io that will allow the loading of packages from npm, jspm.io and you have astopgap package manager native module syntaxloading progress and systemJS is biased towards and tracking with the like systemJS something Personally, Ithink the path forward is to use do in 2016 while this is all in flux? So, the question that is is left this: what should one and loading is natively implemented. likely remain unsolved until native module syntax and answered in different ways for much of 2016 and The questions Iam raising will continue to asked be fragmentation itself? than we not risk causing more confusion and problems By combining the needs of both into asingle tool, do developer as first class citizens. Is that even possible? to treat both the front-end developer and the Node Additionally, asingle package manager would have and jspm.io and . Why? Because . Layer on © 2017 Progress. All Rights Reserved. my loader/dependency manager. go get afocused tool that is not tightly coupled to like serving and reloading my development code, I'll Personally, if Ineed another tool to do another job, does, in fact, do more. And, if you want more, use it. some will argue that webpack does more. And it of module syntax, packaging and loading. However, is nothing lacking in terms (except astopgap) it's I've found that between systemJS &jsmp.io, there tool to install third tools/code/plugins. party need apackage manager, they just need asimple npm alone onto others. Many developers even don't but dogmatically don't push asubjective mantra of using npm alone, Isay do what works best for you you and then use it to write ES 2015 modules. for As simply pick whichever one makes the most sense to problem. I'd suggest you stay clear of dogma and Both webpack and systemJS solve the same core alone. into npm using militantly developers shaming A lot of developers are flocking to webpack @runspired sentiment from the with the matter is in the minority. Alot of people agree However, from what Ican determine, my opinion on
@runspired improving npm instead of starting over.” a path to get it there, and we should work on “Yes. not Npm has perfect, won. It's but there's Contents : and and 11 topics below seem to the be pressing issues in 2016: order, unresolved the non-critical In language. the 2016 will continue to ayear be where we fill gaps in clearIt's that even with the major update in 2015, JavaScript will need to resolve? that future updates to What issues will remain in 2016 • • • • or step aside. step or addressed and webworkers will have to step up processing) in JavaScript will need to be Concurrency might agood be idea. promises). And O'yeah, canceling apromise. That will need to used be throughout (e.g. HTTP eventuallycomplete. Promises and streams await functions will help, the journey is far from We haven't fully scratched the async itch. While, implementation to commence. will need will need to ironed be out and an initial How native modules are loaded in abrowser and parallelism and (i.e. parallel
© 2017 Progress. All Rights Reserved. same concern: same notI'm alone in this observation, Brendan shares the practices. thatfacilitate best variations styles of to update our thinking and education on several JavaScript applications. Thus, in 2016 we'll need in significantly different used styles for constructing also start to experience feature overload resulting The last thing I'd like to note is that in 2016 we might 2016. youAs can see, we have more work to get done in issue. to project. In 2016, we'll have to address this potential easy for JavaScript developers to jump from project With more ways of doing things right, it won't as be • •
Brendan style.” squint at some and code know the layout and ways of doing things, so it is not easy as to concern“My is that there are now even more Contents regular browser. regular in amobile browser with the same status as a JavaScript to treat the runtimes manufacturers Lastly, payoff whomever it takes for all browser immutable native objects The should we or shouldn't we debate about will hopefully conclude. 12 © 2017 Progress. All Rights Reserved. this! potentially cause amajor disruption. Keep an eye on there are whispers are there I should, however, mention that as Zakas mentions, the most used programming language in the world. continue its dominating march in 2016 to becoming The reality is most people believe JavaScript will decline. Zakas Nicholas C. in the spotlight in 2016. Beyond 2016, some, like concludes that JavaScript will remain on center stage future, the consensus from the questionnaire 2016. It would seem that in terms of the immediate JavaScript's popularity and usage will dwindle in or opinion that would lead me to believe that haveI don't and find a persuasive Ican't reason use? Will JavaScript continue to rise in
Nicholas Zakas C. JavaScript.”future of thatOnce all happens, bets are on the off more, being written directly for the browser. experimenting with Java, Python, Ruby and that to the browser means we'll see people to compile down to WebAssembly and deliver about alternatives to JavaScript. The ability browsers, will start freeing up people to think think“I WebAssembly, once available in all Contents , were willing to forecast apotential web assembly web that could 13 things like NativeScript.things I'd suggest you start applications? If you find that to an be impossibility, 2016 JavaScript became the language of native JavaScript is the language of the web. What if in JavaScript alone. want to they write because precisely applications React Native React developers will turn to solutions like NativeScript used to create native applications. My prediction is and more languages that in the past have been further its ubiquitous seeding by replacing more Most believe, as Ido, that in 2016 JavaScript will and Electron and wrapping your head around wrapping to create native native create to ,
© 2017 Progress. All Rights Reserved. turns out this is rather difficult to measure. Is JavaScript really as popular as it appears to be? It JavaScript. in Explosion Cambrian this of popularity There has been some debate over the true tools. miscellaneous and JavaScript frameworks libraries, commonly referred to as a“Cambrian Explosion” of of the JavaScript language has resulted in what is implement consistently. The recent rise in popularity that browsers either provide, don't or don't functionality APIs and to supplement frameworks Web developers have long relied on libraries and Libraries Frameworks and JavaScript of frameworks. and libraries composed this chasm. The bridge on which they migrate is Many developers are already beginning to cross languages. into the age of legitimate application development JavaScript brings that forward leap monumental a evergreen standards, compliant browsers and ES6, building modern applications. Onthe other side are and ES5, alanguage woefully inadequate for differing standards, competing module systems great divide. Onone side are legacy browsers, JavaScript developers stand at the edge of a Frameworks
Contents 14 proficiency. appears to more be of a“market value” of language and their own IEEE Xplore library. This measurement postings CareerBuilder GitHubstats, of combination language, with Cas aclose second. This measure is a Spectrum IEEE ranks Java as the most popular © 2017 Progress. All Rights Reserved. GitHub Linquist library Linquist GitHub the pushes. Detection for languages in repos is done by total and repositories active most the with language JavaScript ranks GitHub, the as on repositories GitHut JavaScript just under Java as of June 2015. ranks StackOverflow, and GitHub on another one Redmonk
Contents , asite that ranks over 2million active , which measures languages relative to . 15 situation is critical mass. critical situation is The libraries. state JavaScript of and the frameworks thisIt's last GitHub statistic that pulls the curtain on © 2017 Progress. All Rights Reserved. jQuery a lot of experience on real world projects. with are implementers some and frameworks, these Some of these developers are the very authors of of the most popular third libraries party available. the community to help us gauge the future of some For this article, we asked several key developers in choice. their critique are hesitant to honestly frameworks those thatadopt those and frameworks find the signal in the noise. Furthermore, creators of build applications makes it even more difficult to which framework or library is the “right way” to around rhetoric The frameworks. numerous the There is also very strong sentiment behind all of business. tools on which to build the digital portion of their difficult for companies to pick aset of JavaScript net result is an environment in which it is extremely of these third libraries party is source open more interesting is the fact that almost the entirety astonishing amount of third software. party Even JavaScript developers are simply with a deluged Critical Mass
Contents . The 16 Brian Ford—Angular Team compare. it hard to have dialog agood about how tools over another was rational. Ithink this makes and others, why the decision to use one tool and so we're eager to justify, to ourselves developers. We invest deeply in some tool, ofsort sunk-cost fallacy—at play with web I think there's ahuge collective anxiety—a © 2017 Progress. All Rights Reserved. is in decline. There is one jump in the top 1million jQuery. There is no inclination that the use of jQuery BuiltWith The predictions for 2016 jQuery provides amuch cleaner API than native DOM code. manipulation or XHR operations, but because jQuery developers to need jQuery perform basic DOM Lindley goes on to explain that this is not because relevant today as it was when it was first written. ” “JavaScript Enlightenment, ”writes that, is “jQuery as There And Back Again In his recent article, “ it is no longer necessary. weathered some rather heavy criticism claiming that isjQuery now adecade old. In the last year, it has GitHub. on repository starred time these words are being it is typed, still the most and widely used JavaScript library in the world. At the cannot denied be that is jQuery still the most popular Whether or not you find yourself afan of jQuery, it
Contents site shows asteadily growing usage of The Relevance of jQuery: Cody Lindley Cody ,” , author of 17 sites still use jQuery. use sites still indication is asteady rise. Over 70% of the top 10K sites during the month of October, but the overall Cody Lindley: jQuery's Relevancy—There and Back Again Back and Relevancy—There jQuery's Lindley: Cody code.” API helps them get more things done with less use it when scripting the because the DOM And the fact most is, developers to choose optionally use when scripting HTML elements. is simply“jQuery ahelpful library that you can © 2017 Progress. All Rights Reserved. or Redux must added be to the React equation. order to achieve that, afull framework such as Flux the actual physical structure of the application. In rendered, and doesn't deal with the flow of data or and are built components visual how with concerned primarily is that React That means implementation. React is meant to the just the Vin any MV* However, it also does far less. brothers and sisters such as Angular or Ember. ReactJS is afar simpler library than its larger captured the hearts and minds of developers. using React, and it cannot denied be that React has this the list of big companies such as Netflix that are past 12 months is nothing short of astounding. Add to ReactJS. The hype that React has garnered in just the with open JavaScript didn't we popular and libraries We would remiss be if we started our discussion of React but the actual utility of the library will remain intact. The level of hype around will jQuery continue to die, otherwise is anecdotal at best. continue to rise during 2016. Evidence to suggest This is a clear indicator that usage jQuery will
Contents 18 identical to the actual jQuery library. jQuery actual to the identical and manipulation subset of jQuery. The API is rather uses jqLite, which is essentially the DOM selection level of DOM abstraction. For instance, Angular 1.x Even newer frameworks and libraries offer some too.” Facebook, it should good be enough for my project The appeal then becomes, good enough “If it's for would applications be like Facebook and Instagram. applications that are already running on React. These the appeal to developers is the large, high load and the way that it handles data binding. However, The main features of React are the virtual DOM, © 2017 Progress. All Rights Reserved. large, it is fragmented and is quickly going the way components. While the React 2016 will also the be year of commercial React a fundamental tenant of programming in general. violates separation of concerns, which has long been in the same place, many have pointed out that it logic and markup for acomponent is contained during 2016. While some developers like that the JavaScript, which will probably reach apeak point around model React's of mixing markup with Developers can expect to see continued controversy applications. well-known large, in use existing Dave Ramsey Every Dollar project based on its Elijah Manor pointed out, React was picked for the largeamong consumer developer applications. As theExpect adoption of React to remain strong React predictions for 2016
Elijah Manor— are two applications that scale really well.” Facebook and Instagram, and obviously, those React was really new, but it came out by We wanted something that would scale well. We were expecting alot of load initially [...]. launching anew product called EveryDollar we started using [React], is that we were compelling“One reason, and the reason Contents Polymorphic Podcast Polymorphic ecosystem is quite . 19 frameworks. introduced will begin to bleed into other libraries and React in 2016. likely It's that the model React has Developers should make it apoint to learn the lack of acomplete story out of the box. conservative shops from adopting React, in light of full application stack. This will keep larger, more and all of the other components needed for a developers to stitch together data access, routing small of part the overall application solution leaves distance in 2016. The fact that React is such a Enterprises will continue to watch React from a comprehensive solutions backed by apartner. of plugins. jQuery Developers will begin to look for The React team did not return a request for input on this article. this on input for arequest not return did team React The Rob Eisenberg—Creator of Aurelia HTML into our JavaScript?” So, why now the eagerness to embrace mixing about not mixing JavaScript into our HTML. an example of this. We've learned hard lessons when you create aframework. React is again learning should taken be seriously into account the authoring of SOLID of Decades code. libraries to assist developers in abandoning see awillingness“I of many frameworks or © 2017 Progress. All Rights Reserved. for Angular, Progressfor including Kendo UI Backbone. There are several commercial UI libraries Compare that with 6,969 for ReactJS and 19,031 for Angular. with are that tagged StackOverflow Currently, there are 132,639 questions on grew drastically. also ecosystem Angular The fans. adoring that has not stopped its adoption and legions of However, frameworks. other with compared when over-engineered is Angular its documentation and performance. Some feel that Angular has received some amount of criticism for structured languages, such as Java or C#. questions for developers coming from more Angular seemed to answer so many outstanding has so completely adopted an open source library. was one of the rare times that the enterprise sector remarkable to watch. It was remarkable because it The rapid rise of Angular during 2014 was AngularJS
Contents and too complicated . 20 2015. behind Angular and 2, what was accomplished in Ford from the Angular team explained the intentions release of Angular 2in the first quarter of 2016. Brian release, developers can safely expect to see the full 2 Angular impending the of announcement the With 2016 for predictions Angular Brian Ford—Angular Team improving.” faster10x than AngularJS and we're 1, only driven We're approach. already muchas as (React, Ember, etc.). We're using abenchmark- other source open projects in the same space everything we learned from Angular and from 1, the core concepts in Angular 2right. We took and robustness. We spent getting most of 2015 Mostly,1 apps. we wanted to improve speed without significant breaking changes in Angular the things in Angular 1that were impossible main“Our motivation for Angular 2is to do © 2017 Progress. All Rights Reserved. web components standard. components web and acomponent model that is compatible with the heavily on ES6, astandards-based module loader to provide afull application framework. It relies Aurelia existing/emerging to embrace tries standards framework of his own, called Aurelia. leaving the Angular team to work on aJavaScript in November when he announced that he would be Durandal into Angular He made 2. headlines again Angular core team, with the intention of merging of 2014 when he announced plans to join the Rob Eisenberg made Internet headlines in April Aurelia experience, which will involve writing guides, building ecosystem] is going to making be migration agood of that [improving tooling, documentation and and enjoyable as possible,” says Ford. “A huge part working hard to make the experience as productive probably notice it has alot of rough edges. We're “If2. you to try get started with Angular you'll 2, developers to migrate from Angular 1to Angular will spend anon-trivial amount of time helping improve significantly in 2015. The Angular team The Angular documentation and tooling will also
Contents 21 this article. on input his for team Angular the from Ford to Brian thanks Special continue to see Angular 1thrive in 2016. especially in the enterprise, where we will likely path is forged. Angular 1will have along tail, Angular 1for 2in 2016, even if asmooth migration unlikelyIt's that swaths of developers will abandon migration.” support tools and making improvements to AngularJS to 1.x Rob Eisenberg—Creator of Aurelia build future-compatible apps.” platform itself and to help developers use it to libraries do, we've chosen to embrace the web even against buck the web itself like some “Rather than invent non-standard or tech, © 2017 Progress. All Rights Reserved. to NativeScriptto JavaScript Native approach for mobile apps, similar may mean that Aurelia has plans to provide asimilar other things we're planning,” said Eisenberg. This we move beyond Aurelia's v1release and on to you'll see the next phase of that vision realized as rich interactive applications on every device. In 2016, Aurelia as aplatform and ecosystem for building a single-page app framework. “We've always seen Aurelia has aggressive plans to far be more than Caliburn.Micro. such as work, previous Eisenberg's are familiar with who developers and momentum, specifically in the .NET community in 2016. This will cause Aurelia to gain significant Developers will begin to adopt ES6 in droves starting Aurelia 2016 for predictions directly ported since it is primarily just ES6 classes. is used in the future, code written in Aurelia can be framework different a or arrives, standard emerging applications are “future proof.” When the next at all. This goes along way to make sure that classes, and not referencing the Aurelia framework possibleit's to build applications using mainly ES6 The most interesting thing about Aurelia is that
Contents and React Native. React and 22 on this article. Eisenberg to Rob thanks Special partnership that Aurelia offers. business the for favorin alternatives, specifically of support will cause many enterprises to choose it having acore team of developers and offering supported by the community. Aurelia's model of frameworks since they are for the most part not technology have been slow to adopt JavaScript is proposition core business whose entities larger on the fact that it is asupported product. So far, More large enterprises will adopt Aurelia based from the Aurelia team for his input input his for team Aurelia the from © 2017 Progress. All Rights Reserved. Document Processing. of Data Grids, Schedulers, Data Visualization and commercial based UI library available. It is also avery successful Today Kendo UI is the largest open source jQuery- offered. wanted access to the robust widgets that Kendo UI Angular, However, Durandal. and Ember still they such as frameworks, standard towards community capabilities, developers continued to gravitate those offering Despite solution. application everything else developers needed for afull to include binding, routing, views, models and While Kendo UI started as aUI library, it grew the way back to IE 7. would guaranteed be to work across all browsers, all could leverage asingle set of UI components that Kendo UI was built on the premise that adeveloper that made it hard to assemble acohesive application. support, as well as awilderness of plugins jQuery drastically different browser versions and feature At the time, developers were struggling with as aset of based jQuery user interface components. Kendo UI was launched in November of 2011, strictly Progress Kendo UI
Contents
library, specifically in the areas the in library, specifically 23 frameworks so that it can plugged be in anywhere. larger various the for abstractions offer and Kendo UI will focus on being aset of UI components, any other framework that developers prefer to use. integration Angular, with React, Ember, Aurelia and own binding framework in 2016 to provide better Kendo UI will begin to decouple itself from its Kendo predictions UI for 2016 Tsvetomir Team Tsonev—Kendo UI Lead thatblocks play well together.” enough libraries. We reusable, need functional “There are too many frameworks and not © 2017 Progress. All Rights Reserved. responsible for future versions of JavaScript. Yahuda Katz, is on the TC39 committee, which is as promises. In addition, one of Ember's creators, the standards in future versions of JavaScript, such standards. It has been an early adopter of many of Ember also places apremium on future web topart its sheer age. as frameworks such as React. This may due be in Ember, it does not get the same amount of attention use application desktop Music Apple even the and popular sites such as Discourse, Groupon, Vine Although many implementations. notable with SproutCore of framework ecosystem. Grown from the remnants Ember has long been astaple of the JavaScript Ember Timeline. additional such complex Interactive widgets, an as these components. Also, look for Kendo UI to ship entail adding new features and continuing to refine PivotGrid and Spreadsheets widgets. This will extremely complex UI widgets, such as the Grid, Kendo UI will continue to invest heavily into
Contents , it is an industry standard framework framework standard industry an is it , 24 input on this article. to Tsvetomir thanks Special Tsonev React. and 2 Angular for other notable frameworks, such as Angular, Kendo UI will also deliver more sample applications Ember for their next releases. massive scale. Look for other large sites to choose large applications that need to service users at a its React and Angular it peers, will the be choice for While it won't getting be nearly as much airtime as Ember will continue to a“sleeper” be framework. predictionsEmber for 2016 practices, so that they fall into the “pit of success.” framework that seeks to guide developers into best code. This is done via use of arigid and opinionated Ember also tries to help developers write better from the Kendo UI team for his his for Kendo team UI the from © 2017 Progress. All Rights Reserved. system, Atmosphere. Developers the add can around aMeteor proprietary package management centered currently is Meteor around ecosystem The client. they want their code evaluated on the server, or the the data store. Developers are then free to choose if MiniMongo to allow client-side code direct access to It uses an in-browser version of Mongo called server-side, the on Node uses with MongoDB. along Meteor falls into the “Full Stack JavaScript” camp. It platform. server tier and database. It is atrue application concept the rest of the way by providing both the JavaScript (server-side rendering), Meteor take the aforementioned allUniversal do such as Angular, Ember or Aurelia. While the frameworks to your application standard compared Meteor is another library that really can't be Meteor comparison in their own minds before deciding More and more developers will begin to draw this React in terms of separating logic from markup. Ember will serve as the diametric comparison for
Contents or Portable Portable or 25 The Ember team did not respond to a request for input on this article. this on input for to arequest not respond did team Ember The much as possible the way Ember dictates. together as React prescribes, or separate it out as if they want to blend all of their component logic subscribers is a non-trivial $495 per month. Galaxy. Right now, the cheapest package for Galaxy Meteor will offer afree tier on its hosting platform, that are built on the technology. Meteor as they learn of some very high profile sites thebe first time that many developers are aware of Thiswill platform. currently that the use applications Meteor will begin to announce large-scale Meteor predictions for 2016 simple command. simple libraries can then pulled be into any project with a Atmosphere format. the with These are compatible necessary meta data to their libraries so that they © 2017 Progress. All Rights Reserved. possible with JavaScript, with possible CSS. HTML and used to create any piece of functionality that is components. However, Web Components can be as the emerging standards for creating interface are the technologies that are generally thought of it comes to Web Components. Web Components the implications on all of these frameworks when This wouldn't aproper be article without considering Web Components on this article. to Uri Goldshtein thanks Special that Meteor would like to close. performance wise from native apps, and this is agap it is on the desktop. The mobile web is still afar cry support in JavaScript frameworks is not quite what 2016 regarding the mobile web. Currently, mobile Look for Meteor to make abig announcement in
Contents from the Meteor team for his input input his for team Meteor the from 26 The main hang-up so far has been browser support. so far kept them from being adopted by developers. the major drawbacks to Web Components that have Production...YetFor “ article, his In Uri Goldshtein—Meteor TeamUri Goldshtein—Meteor experience than native apps.” [closing that gap] but it is still not abetter still not there. There are many paths for frameworks] is true mobile support. We are believe“I that the biggest [gaps in existing Why Web Components Aren't Ready TJ VanToll TJ ,” describes several describes of © 2017 Progress. All Rights Reserved. to polyfill as Web Components are. not used be by developers, especially as hard if it's not supported in Mobile Safari, likely it's that it will holds the rest of the web hostage. If atechnology is choice of browsers on iOS, Mobile Safari currently Safari altogether. Unfortunately, since users have no and Mozilla, Apple removed Shadow DOM from At one point, despite agreement from both Microsoft those standardsthose supported. widely become own technology for Web Components standards as All JavaScript frameworks will begin to swap out their recentthe addition of Shadow DOM to WebKit the second half of 2016. This prediction is based on All major browsers will support Web Components by 2016 Web Components predictions for
Production...Yet TJ For VanToll—Why Ready Aren't Web Components Components outside of Chrome.” necessity for developers that want to use Web it happens at all, is along-term apolyfill won’t possible be for avery long time, if in Safari Because cross-browser or IE. support support in Firefox, and they are not present landed in Chrome they 36, only have partial is browser support. Although Web Components obvious“The reason to avoid Web Components Contents . 27 Brian Ford—Angular Team they more become available.” to pragmatically adopt new browser features as smaller The general parts. idea is for Angular than one way to break apart your app into a bunch of upcoming APIs, and there's more Components”“Web is an umbrella term for © 2017 Progress. All Rights Reserved. from. from. compatibility issues that Web Components suffer support. This is most likely due to the same browser arena, Polymer has not yet garnered mainstream entirety of their influence into the Web Components Despite Google throwing what appears to the be exist.APIs don't (such as Shadow DOM) for browsers where those attempts to polyfill certain Web Components APIs that is built on the concept of Web Components, and framework application an is Polymer Components. mistaken for, and used interchangeably with Web The Polymer project from Google is often Polymer
Contents 28 properties, such as Google Play Music. GE. It also includes many of Google's own internal These include some big name companies, such as that there are now 1million sites running on Polymer. At the 2015 Chrome Dev Summit, Google announced Design. especially if they are interested in doing Material virtually everything they need for their applications, Developers looking to adopt Polymer will find even seamless integration with Google's own APIs. for Polymer that encompasses animation UI, and Google has created an impressive list of components © 2017 Progress. All Rights Reserved. article. this on input for to arequest not respond did team Polymer The Components by the later months in 2016. toExpect see the first batch of commercial Web long. so developers who have been coding to frameworks for of 2016. This will cause an identity crisis for web development community during the second half Web Components will begin to take hold in the 2016. These are already on the roadmap. in internationalizationPolymer for and components Google will release application framework, routing internally. push Web Components and Polymer by adopting it adoption, it is clear that Google will continue to advantage. Given that it has little developer obviously sees Web Components as astrategic its applications over to Polymer in 2016. Google toExpect see Google transition the majority of 2016 for Polymer predictions
Contents 29 input for this article. this for input research and conversations with those who provided developers that Igathered based on my own Lastly, here are some generic predictions for Final developer predictions • • • • and Aurelia to get in this game as well. React Native and NativeScript. Ember Expect than the web. This is already happening with JavaScript frameworks will begin to target more mastered. essentiallyhas been based on the fact that fundamental polyfilling Browser compatibility will largely anon-issue, be it. Developers will expected be to know ES6. Learn and Aurelia all support it. seeing as how React, Angular Meteor, 2, Ember Universal/Portable JavaScript will big be in 2016, © 2017 Progress. All Rights Reserved. skyrocketed in popularity. The list of companies Node.js was first written in 2009, and has since runtime to succeed at doing so at scale. run JavaScript on the server, Node.js was the first plenty of companies and frameworks had tried to based on Google’s V8 JavaScript engine. Although Node.js Node.js engine Google’s entry into the browser and JavaScript ago running JavaScript on aserver was unthinkable, these “new frontiers” is performance. Whereas years Part of what’s driving JavaScript’s expansion into ecosystem that JavaScript hasn’t influenced. robotics controlling side code, driving iOS and Android apps, and even JavaScript server- as With running now applications. been used in an increasingly diverse set of software language designed for use in web browsers, has In the last several years JavaScript, ascripting JavaScript’s Frontiers New
Contents world in 2008 sparked aperformance is an open source runtime environment , it’s hard to find asoftware 30 from the Java and Ruby worlds. twice as many modules as similar package managers software world in 2014 biggest the package became managernpm, in the PayPal and Microsoft. The Node.js package manager, Foundation Node.js recently formed using the and Node.js enormous, is JavaScript’s first new frontier: Node.js. directly. Let’s start by looking at what is perhaps key developers involved in building these solutions applications. We’ll get the perspective from many side JavaScript, build mobile apps desktop and JavaScript frameworks being used to run server- In this article, we’ll look at what’s next for the have only furthered this effort. the language. More recent such efforts as asm.js of improvedspeed drastically that the competition includes the likes of IBM, Intel, , and now contains nearly
© 2017 Progress. All Rights Reserved. merged in June 2015. were fears Node.jsthose averted when and io.js term fragmentation in the Node.js world. Thankfully, and community support, leaving many to fear along- The new framework, io.js active and new contributors and the lack of releases. framework popular forked the growing pains. In late 2014, agroup of developers However, the success of Node.js hasn’t come without modulecounts.com from manager. Image apackage as of npm Growth
Contents , quickly gained followers , citing the lack of 31 . that release for afull 18 months. per year an LTS release, and will actively support Under the plan, Node.js will designate one release or aLong-Term Support plan for Node.js releases Part of the merger involved the formation of an LTS, . © 2017 Progress. All Rights Reserved. JavaScript aimed at providing better support for client-side to continue as well, as npm’s recent releases have theExpect exponential growth in modules on npm enterprise solutions like Java.typical and .NET in Node.js adoption in the enterprise—replacing such as long-term support plans, may signal agrowth Progress, etc.—as well as enterprise-friendly features of Node from large companies—Microsoft, IBM, Intel, The continued package managerits npm. adoption In 2016, expect to see further adoption of Node.js and in 2016 Node.js coming for Node.js in 2016, he had this to say: from the Node Foundation what the biggest change the future of Node.js. When Iasked Mikeal Rogers the development cycle has major implications for release they can count on for years to come. And as well as large companies that need astable developers that want to stay on the cutting edge, The development cycle is aimed to appease both
Mikeal Rogers, Node Foundation Node Rogers, Mikeal enterprises to expand adoption well.” as for developers and anew opportunity for truly had LTS before so this is all abig change significantly more than before and we’ve never releases receiving Long Term Support. That’s releases each year, with only one of those the biggest change. We’ll have two major new“The development cycle is going to be Contents , thus replacing the need for client-side 32 ecosystems. reason for npm’s growth is that it is an ecosystem of grow. In fact, according to Mikeal Rogers, the major plugins npm on jQuery and scripts client-side their registering developers start JavaScript package managers such as Bower. As ecosystems.” getting replaced by new, rapidly growing that ecosystem are leveling but off they keep platforms for avariety of Parts use cases. of ecosystems. It’s the best place to build sub- it forward is that npm is an ecosystem of npm’s growth, you’ll see that what is pushing even Iwas shocked by. If you dive deep into which fewwithin a days we what predicted, of wouldn’t level out. We hit modules 100K modules and that100K the rate of growth said that in alittle over ayear we’d have over time thought people it was insane, because it of npm and created apredictive graph. At the “A few years Iquantified back the growth rate Mikeal Rogers, Node Foundation Node Rogers, Mikeal , npm’s reach will only © 2017 Progress. All Rights Reserved. most influential people in 2012. notorious complaint a perception of bad performance, with the most Over the years, Cordova has defended itself against Cordova. to contribute many that source companies framework as Cordova. Today, Cordova is afree and open Software Foundation and the project became known PhoneGap source code was donated to the Apache 2011 October in Adobe created by Nitobi in 2009, and was acquired by to run native mobile apps. PhoneGap was originally JavaScript using for mainstream solution first the for running JavaScript on the server, PhoneGap was Much like Node.js was the first mainstream solution CordovaPhoneGap and popularity. And as npm grows in popularity, so does JavaScriptAs grows in popularity, npm grows in you an idea of the sheer scale npm operates at now. “ for npm as apackage manager. Aquick npm search NativeScript—all Native and Cordova, React use JavaScript article—including this in solution evidenceAs of this claim, basically every other , and PhoneGap is an Adobe-owned distributor of
Contents jquery ”, “ ”, polymer coming from one of technology’s ”, “ ”, . As part of part . As the acquisition, the meteor ”, or “ react ” can give 33 JavaScript apps. to drive mobile don’t run JavaScript on the server, but rather, use Let’s shift our focus to some technologies that framework. mainstream server-side JavaScript first world’s Node.js. The future looks bright for the software Mark Zuckerberg, Facebook wasn’t there.” HTML5 opposed to as native… because it just made acompany as is betting too much on years, Ithink the biggest mistake that we I’m introspective“When about the last few © 2017 Progress. All Rights Reserved. Studio. development options involving Xcode and Android web developers, especially when compared to native HTML, CSS and JavaScript will continue to appeal to The Cordova approach to building mobile apps with their toes into the waters of mobile development. large companies, many of which are just dipping Much like Node.js, Cordova’s stability will appeal to 2016 in Cordova Cordova. LeRoux Brian asked Cordova performance situation. With that in mind, I WKWebViewnew API Android’s views web as auto-updating new features provided by mobile OS makers, such In addition to company provided performance aids, TelerikThe Marketplace Plugins Verified Onsen frameworks UI likeperformance-minded Ionic to attack this performance problem. This includes Since 2012, anumber of companies have stepped in
Contents , and Kendo Mobile UI of Adobe about what’s next for , have greatly improved the the improved greatly have , tooling improvements improvements , tooling iOS’s iOS’s and , 34 Telerik Verified Plugins Marketplace high-quality plugins, such as those found in the views such as those provided by Crosswalk from Progress and the PhoneGap team Brian LeRoux, Adobe LeRoux, Brian distribution.” own this unless they extend Cordova with their happy.me The end dev audience won’t see mindset is beginning to take hold which makes few years of thrashing, but ‘small modules’ M and possible. much as 9as iOS It took a on top of platform upgrades like Android features out to the plugins interface, and stay We strive to keep things simple, push the “Cordova has grown very deliberately stable. . , new web , and © 2017 Progress. All Rights Reserved. possible performance. possible that in fit on the native OS and offer the best platform’s native user interface APIs to build apps (rather than Java, Swift and so forth), and use a apps: use JavaScript to write your application logic best-of-both-worlds way to build iOS and Android JavaScript Native frameworks attempt to offer a involved. their user interfaces; there is no browser or web view a platform’s native controls and paradigms to build PhoneGap-based apps, JavaScript Native apps use known as “ of JavaScript-based mobile app development The year 2015 saw the emergence of anew category Native mobile apps applications. native mobile JavaScript JavaScriptthe using world: truly to build development from comes recent a development in The bigger immediate challenge to Cordova concept of progressive apps in 2016. however, expect Google to continue pushing the features are still only offered on Chrome for Android, Progressive apps are still in their early days, and their screens, home screen placement and offline access. web apps with native-like features such as splash is pushing the concept of progressive apps differenttwo angles. The first is from Google, who its development approach is being challenged from Cordova toAlthough continues grow popularity, in
Contents JavaScript Native .” Unlike Cordova- and , or true 35 code. source JavaScript. the out with Check built apps of mobile Example © 2017 Progress. All Rights Reserved. stability. frameworks in 2016, and both echoed this focus on product manager, about what’s coming for their React Native team, Stoychev and Valio I asked (aka Chedeau Christopher Vjeux) Cordova. Here are afew: drawbacks when compared to frameworks like haveJavaScript some can Native frameworks JavaScript can sound appealing to web developers, with native apps building of idea the Although JavaScript. with native truly apps building so forth—but they share the high-level approach to JavaScript from APIs Android directly and iOS NativeScriptJavaScript access you lets framework, for instance React Native lets you reuse the React js 2015; followed by others, such as Fuse JavaScript Native frameworks to publicly release in Native React . Different frameworks offer different features— different offer frameworks Different . • • •
Contents active developmentactive for many years. mature than frameworks that have been under are less themselves frameworks The tutorials. and as such, there are fewer examples and Finally, JavaScript are new, Native frameworks apps. apps, just like it is in native iOS and Android managementmemory can aconcern be in larger JavaScript are native Native apps, apps Because app. simply using HTML as you would in aCordova APIs for building your interfaces, rather than a browser, you have to learn framework-specific JavaScript use don’t Native frameworks Because and NativeScript and were the first and tabris. and , NativeScript’s, from the , and 36 Valio Stoychev, Progress will continue throughout 2016.” with the Angular 2team, which we anticipate experience. Our other major focus is our work tooling to improve the NativeScript developer working on things like performance and debug applications. Therefore we intend to continue they can count on for building real-world make sure our users have arobust framework “As our user base rapidly grows, we to need Christopher Chedeau Facebook (Vjeux), quality mobile apps they want to.” at Facebook and outside can build the high This edge fix cases… messages, way engineers improvement of all the core APIs, better error performance on done tooling/optimizations, solid. You should see alot of work being enter the phase where we to need make it it was a crazy idea/prototype and now React“For Native, we exited the phasewhere © 2017 Progress. All Rights Reserved. NW.js was developed at Intel, and released back in 2011 in back released and at Intel, NW.js developed was skills. developers with existing JavaScript development Java—especially considering many companies have Objective-C/Swift, as well as Android Studio and compared to building an iOS app with Xcode and Native frameworks offer acompelling option when JavaScript native UIs, with native apps that need will around be for some time to come. For companies JavaScript native approach to building applications showcases NativeScript’s and Native’s (see React frameworks showcases these with built being already applications quality scale usage in 2016, but the number of high- apps generated in 2015 will transfer to large- Time will tell whether the hype JavaScript Native apps. Telerik Platform Progress being created around those frameworks, such as feature set, expect to see an increase in tooling like React Native and NativeScript solidify their for JavaScript Native apps in 2016. frameworks As 2016Expect to the be year of stability and adoption JavaScript Native in 2016
Contents for building NativeScript NativeScript building for ) suggests that the
37 The firs The way into this picture. their JavaScript-based working are slowly solutions article, this in discussed ecosystem software other something like Java or Adobe Air. But, like every & Windows Forms, or cross-platform interfaces using Mac app you’d use platform-specific tools like WPF Traditionally, if you wanted to build aWindows or apps Desktop applications. desktop traditional world JavaScript is creeping into—the same is true of software only aren’t the apps native mobile And app. programming languages to write anative mobile do JavaScript developers have to learn native frontiernew for JavaScript longer No developers. JavaScriptOverall, exciting represent Native an apps desktop apps. desktop internally, works somewhat similarly to Cordova, but for NW.js open sourced in late 2011. Node-WebKit, now called Node-WebKit, which was created by Intel and was because of its switch from WebKit to Chromium t JavaScript-based solution in this space was © 2017 Progress. All Rights Reserved. also takes the approach of using web technologies Slack—which isn’t built on NW.js or Electron, but apps. With the likes of GitHub, Microsoft and even platform JavaScript-based tools for building desktop article, the future seems bright for these cross- Like many of the technologies discussed in this Desktop apps in 2016 development in the has become community. Electron resources a quick community-created look through of alist new headlines in 2015 as the engine behind Microsoft’s starts NW.js’s with up 25,000+ GitHub on starts 20,000 over has backing, Electron has surged in popularity, and now GitHub’s With any in project. to use decoupled GitHub’s web-based text editor, and has since been Electron was developed as the shell for Atom 2015 April in released was GitHub’s Electron web technologies. Linux desktop applications using standards-based The combination lets you write Windows, OS Xand such as the file picker, window menus and so forth. shell, while providing access to native desktop APIs, NW.js packages up aweb application in anative
Contents cross-platform Visual Studio Code IDE shows just how popular Electron ). Electron also made made also ). Electron (quickly catching catching (quickly , and and , , 38 end to where JavaScript can go. programming language—and there seems to no be rollovers, to perhaps the world’s most popular gone from atoy language for handling image mainstream. In less than adecade, JavaScript has in these contexts has gone from unthinkable to same: in the span of afew years, running JavaScript the apps—the narrative been has desktop and apps disparate of set topics—server-side mobile code, seemingly a discussed has article this Although JavaScript’s new frontiers in 2016 applications you’ll see launching in 2016. and others to drive many of the new desktop technologies. projects Expect like NW.js, Electron feel confident building desktop apps with web to build anative app—other companies can building cross-platform apps. desktop Electron announced GitHub 2015, architecture. such April using an In framework Fast forward afew years and NW.js is not the only , asimilar framework for © 2017 Progress. All Rights Reserved. Facebook’s scale, as Christopher Chedeau shares: Christopher Chedeau as scale, Facebook’s use today. This is even aproblem at acompany at number of operating systems and devices people developers with the expertise to reach the crazy especially small companies, cannot possibly hire build software for multiple paradigms. Companies, is the desire for asingle development model to One of the reasons driving JavaScript’s growth Apple TV. tvOS recently announced Apple’s on native apps offered asbeing afirst-class citizen for building on hardware through projects like Johnny-Five space enough to cover in this article, such as running JavaScript has reached places where there wasn’t statement has never more seemed prophetic. JavaScript,” in written eventually be that and JavaScript, in written will be can that application In 2007, Atwood Jeff stated famously
knowledge base…” packageas manager, core libraries, IDE, each ecosystem has the same tools such is that there is amassive waste as of effort