Frameworks such as Javascript:angular in the 2015 will be replaced by libraries

Frameworks such as Javascript:angular in the 2015 will be replaced by librariesYoung2014-12-16

Note * This article expresses the view that the holistic solution such as angular and ember will be smaller and more focused (with an excerpt), and some previous articles have also expressed similar arguments: We don't need a JavaScript framework , What's wrong with angular.js?

The world of JavaScript seems to be entering a loss-rate crisis. New framework technologies are being rolled out and popular at unsustainable speeds. But I think that society will adapt and adopt a new, responsive approach. I believe that developers will move from a holistic framework (frameworks), such as Angular.js and Ember, to a series of small, combined, professional libraries to mitigate the risk of loss and allow solutions to compete separately in different areas of concern.

Let me explain.

Stir

If you have not previously paid attention to the angular community, at the October 2014 Ng-europe (Europe) Conference, the angular development team revealed some roadmap for a significant update of the angular 2.0. More controversially, NG2.0 will not be able to be backwards compatible with the existing angular code. In fact, some key concepts will be put on hold. The development of angular will have to master a new framework.

Understandably, this upset a lot of people. Whether right or wrong, the knowledge, methods, experience and code that developers have worked so hard to gain over the past two years are now freely deprecated. Even worse, there is no transition. The new project will be released at the end of 2015, 12 months later, and opponents feel that Angular2.0 may be "born dead".

Honestly, I'll give it up no matter what changes the angular team made in version 2.0. Emphasize off-line functionality and give up support for old browsers to make new things sound great.

But it's a mess. The syntax looks like dog poop, and the huge gap between this and 1.3 means that our real job opportunities, which have survived for many years, have been backed up. I can't tell my boss that we're going to build something incredible, but we need to plan a code that doesn't have new features until 18 months after rewriting the code.

by Jbarkett, Reddit comment

There are a lot of unpleasant comments pointing specifically to angular and Google-some of them are pertinent, and some may not. But one of the highest votes is not about angular. It points to the entire JavaScript environment:

As many people here see, fashion web development now becomes a joke; I'm very serious and glad I found my way. Once you are forced to deal with this meaningless thing, you either scream out or go crazy. It doesn't even have a fragment combination. I've lost interest in the MV Framework, and I've defined the framework as a combination of "use Foo,bar and Baz", where Foo is the event library that you've never heard of, with 3% of the usage share; Bar is the template library you've never heard of, with 2% shares; Baz you've never heard of 1% of people using data-bound libraries, making combinations useful?...... I don't know, maybe, the author will switch to a new library in the next five minutes.

I don't understand. I don't understand why some people think it's a good idea. I've seen the code generated with this thing, it's incredibly scary, because no one has time to understand anything that it's changed in 30 seconds.

by Othermike, Reddit

Othermike's problem, in my opinion, is really the problem of customer churn. There are too many damn javascript frames, they change too damn fast.

Two years ago, JavaScript celebrated its revival in a blaze of lights, thanks to a move towards a more modern, more prescriptive browser (such as not internet Explorer) and node. js, as a tool technology for front-end building. New technologies have emerged in different ways. Only 12 months seems to be the case, and the modern network will be dominated by Backbone.js (perhaps marionette), with grunt as a task-driven, require.js and handlebars as the base template. However, over the past six months, these techniques have been clearly superseded, as blogosphere has become--and now, everywhere is about Angular,gulp and browserify. Now the stack seems debatable.

Note * JavaScript build (Yi) system big battle: Grunt vs. Gulp vs. NPM

Can the pace of change last?

I frankly admit to being overwhelmed by my constant exposure to new technologies.

by noname123 Hackernews

Innovation is great, but the wastage rate seems too high. As developers spend a lot of time mastering new frameworks and technologies, they cannot guarantee their longevity. Programmers want to write-what they want to build. But how can we make something when we spend most of our time learning new frameworks? When we are groping with unfamiliar high-tech, how can we be like a craftsman?

Not without hope.

The reality is Yan June. But people are smart, developers are resourceful, and the basic requirement to write a new application is not to let anyone give it up. So, what should we do?

I think there are three major lessons that we can summarize:

1. Cautious and skeptical about new technologies. Take care to put some of those cool new GitHub projects into production. Wait until the popularization has begun to adopt again.

2, do not believe too big business to do things. It's not the first time Google has done this kind of thing. Their interests are not always the same as yours.

3, prefer to use a dedicated library to replace the overall framework. When you choose a framework, you make a big, long commitment period. You need to understand the various workings and strange behaviors within the framework. And what you have in your hands. If the framework proves to be wrong, you will lose a lot. However, if you choose from the library and you can afford it, the library is free to change and you have time to rest.

Libraries (Library) > Frameworks (frame)?

After the controversy in angular, another article on Reddit asked: What technology should the JavaScript developers migrate to.

Here's what the JavaScript program should do:

React.js and Flux (a library with view view-only and event-driven modules)

Ember.js (MVC framework)

Knockout.js (View Gallery)

Backbone.js (MVC framework)

Meteor (Homogeneous frame)

Mithril (MVC framework)

Ember (MVC framework)

' Don't frame, just need a bunch of libraries to do it '

Vue.js (View Gallery)

Breeze.js (Database model-only)

Ractive (View Gallery)

Original address: www.breck-mckye.com/blog/2014/12/the-state-of-javascript-in-2015/

Frameworks such as Javascript:angular in the 2015 will be replaced by libraries