Retrospect and prospect of javascript:2015 year

Links: http://www.sitepoint.com/javascript-2015-review/

JavaScript has gone through an extraordinary year. Although it has been 20 years since May, the news, projects and interests on JS have continued to multiply. Maybe it's a strange cycle, but I can't think of another technology that has a similar pace of development. JS is becoming more and more difficult to keep up with, so I hope this summary article will help you understand JS better.

ECMAScript Rapid Development

Seven years of long wait, in June 2015 ECMAScript Harmony or ECMAScript6.0 specification officially released.

ES6 was soon called ES2015, though I don't know who called it that way. The change of name is good; 2015 the specification was completed. The JavaScript engine now fully supports ES2015 and is understandable to everyone. Unfortunately, marketing doesn't like it; nobody calls ES2015, it seems like January 1, 2016 It sounds out of date.

What does ES2015 mean for developers? Be prepared to do something like this:

• Classes
• Enhanced Object literals
• Let and const
• Arrow functions
• Template strings
• Iterators
• Generators
• Destructuring
• Proxies
• Weakmap and Weakset
• Symbols
• Promises
• Reflection

Most of them are grammatical sugars. For example, JavaScript will save prototype inheritance but provide classical inheritance, for example for developers who migrate from other languages to provide a class structure.

ES2015 support is still incomplete, but you can use converters such as Babel to convert most of your code to ES5. This is also good but additional work is required to make testing and debugging more complex. Personally, I am a JavaScript luddites molecule prefers old stuff until its support is improved.

But forget ES2015 from now on--let's keep es7/2016!

JavaScript Avengers Alliance

With the announcement of Webassembly, a frenzy was aroused; a low-level two-dollar wrapper class collection of Web languages!

Publishing a large application to a browser is not always feasible. A game or complex program needs to download hundreds of trillion source code, compile it into bytecode, and eventually run it in machine code. Webassembly makes this process more efficient by compiling the source code into a simpler/faster processing, the JavaScript engine is compatible with bytecode and packaged in a compact binary file. The browser code will therefore download and start faster. There is no need to run faster than normal JavaScript, but it can be optimized.

We've seen binary land before. Flash, Silverlight, Java, and Google Native Client (NACI) are all similar. But webassembly should have a better chance of showing it.

1. Need for a relatively simple JavaScript engine change

2. The browser plugin is not required and

3. Need Google, Microsoft, Mozilla and Apple support

Are you excited? You'd better brush up on your C + + skills because they are the first target of the webassembly editor.

node. JS Fork
node. JS has become a must-have technology from 20,141 niche technologies to 2015. node. js is ubiquitous; desktops, servers, Raspberry Pi, embedded devices, etc. Even more developers in other areas use node. js to build tools such as grunt and gulp.

2015 witnessed a partisan debate about node and ended with a merger with Io.js. This means that node. js v0.12 will be replaced by node. JS v4.0 in September. Yes, this is a 3 full version of the jump because Io.js has reached version 3.0 and cannot be reversed.

Of course, the version number doesn't mean anything ... In addition to those who now think of node. JS 4+ is more advanced than Ruby 2he Python 3. V5 will arrive in one months, and he will replace it. NET4. and will catch php7! in speed.

Frame fatigue

2,269 new JavaScript frameworks were released in 2015. I made up these numbers absolutely no research, but few people would suspect. It's hard to chase these frames ...

• Angularjs is still popular but has been stabilized in use, and it will be updated in 2016 with the release of version 2.0.
• React has attracted a keen interest.
• Meteor promises a full stack isomorphic JavaScript application platform.
• The vue.js reached version 1.0 and Aurelia released.
• Ember, Knockout and Backbone.js are already alive.
• Others, such as Rendr, seem to be popular, but they are not.

It is impossible for JavaScript developers to rely on a particular code base for confidence. For the integration framework can solve many problems but also can cause a lot of problems. Relying on a framework is very risky, according to this article--front-end JavaScript dependency is a wise recommendation that is completely wrong and requires extracting the underlying technology of the framework.

If you have to use a framework but never think long-term is feasible. New, better frame alternatives appear when you're halfway through the development. Never forget that the framework is an option-you don't have to use it. Small and flexible, minimal dependency projects are a safer bet.

Tool Wave

Do you remember those carefree days, web development requires only a browser, a text editor, and an FTP client. Now you need node. js, Gulp/grunt, git, static HTML generator, Sass Editor, Autoprefixer, Minifiers, Uglifiers, linters, browser sync and a series of other build tools to come up with a basic " Hello World page.

This is good. We are developing more complex web programs that enable us to automate mundane processes and focus on more interesting and tricky parts. 2015 is a great year because:

• Atom 1.0--github's node.js-provides a controllable editor, which was released in June
• POSTCSS-Fast, modular CSS processor, get my tool award this year.
• A range of new browsers include Edge and Vivaldi enhancements to many development tools.

Yes, despite all these free optimization tools, the average page weight is 2MB and contains more than 100 individual files. Is this progress? Maybe not, if you've read this article of Klint Finley, I've closed JavaScript for one weeks, and it feels great. In fact, this is not a technological error, it is a practical aspect. Turn off JavaScript ads, pop-ups, dialogs, unlimited scrolling pages, social registration tips, newsletters, and other features we think are important on Web pages.

Some companies want to stop the web as a bad alternative, such as Facebook instant and Google accelerated Mobile pages. I don't believe an isolated, nonstandard web is the answer.

At last

According to the official news: node. js is better than PHP! Admittedly, this article did not make such a statement, but it shows that node. JS has arrived. Maybe PHP is improving the speed of version 7 to win, but finally use any language that makes you feel comfortable. Controversially, recently they wordpress.com the front end from PHP to node. js. But I suspect more about the state of the COLYPSO project than the language.

The technical term for 2015 is "isomorphic". SitePoint has been discussed, providing sample code. But in fact this means that JavaScript code can work anywhere--either in a browser or on a server. For small standalone applications it is relatively simple at first, but quickly becomes extremely complex.

The JQuery 3 was first released in July. Commitment to release two new versions; one for modern browsers, one compatible version includes compatible IE8. The team is looking forward to some successful breakthroughs.

In November, Mozilla announced that they would stop selling JavaScript-powered Firefox operating systems for smartphones.

This is not the end of the Firefox operating system-development continues and is applied to some smart TVs-but these signals are not good. Perhaps the best bet is on some of the unknown operating systems installed, offline Web applications?

The most surprising JavaScript company of the 2015 comes from Microsoft:

• Visual Studio Code, a new cross-platform extension, similar to the sublime Text/atom editor
• Vorlon.js, an open source remote debugging and testing company,
• Chakra, Edge's browser engine,

Given the recent development of the network, perhaps we should turn the company into a "new Microsoft"?

Outlook 2016

The attitude to JavaScript has changed. A few years ago (unfair) JavaScript was ridiculed, although it was hard to understand, programmers avoided the scripting language with bugs. Now that you can't avoid the language, the 2016 development of tools, frameworks and projects will continue.

It's not easy to keep up, but returning to JavaScript won't be too much of a problem.

Retrospect and prospect of javascript:2015 year