Version 2.0 of the up-and-coming JavaScript framework, Vue.js, has been released, offering a refreshing change of pace in the frenetic world of JavaScript.
In a blog post, Vue creator Evan You says version 2 offers significant performance benefits while maintaining its svelte download size:
The rendering layer has been rewritten using a light-weight Virtual DOM implementation forked from snabbdom. [This] provides significant performance improvements compared to v1, and makes Vue 2.0 one of the fastest frameworks out there.
According to the 1.0 to 2.0 migration guide, "About 90% of the API is the same". Unlike the dramatic change seen from one version to the next with some JavaScript frameworks, with Vue 2.0, "the core concepts haven't changed".
Beyond just the core library, the vue-router
and vuex
libraries have been updated to version 2 and the vue-cli
tool scaffolds projects in 2.0 format by default.
When version 2 was first announced, You said that filters were going away. That stance changed over time and text interpolation filters were left in. Indeed, the filter documentation says "Vue 2.x filters can only be used inside mustache bindings. To achieve the same behavior inside directive bindings, you should use Computed properties instead." The framework doesn't ship with any filters built-in and array filters (ones that whittle down an array based on criteria) have been deprecated.
Because Vue isn't primarily built by a large technology company, You has taken a different approach to funding. He is able to work on the project full-time thanks to a Patreon he set up which lets people pledge a certain amount on a monthly basis. As of this writing, the Patreon funnels $8,853 per month towards the continued development of Vue. In addition to You, there are 18 other people on the Vue.js core team.
The community responded in a mostly positive way saying, "Vue is much leaner than ng2" and "I find Vue 2.0 as something between Angular 1 and React. It's modern and really easy to learn and use".
Vue has published a comparison guide that shows how it differs from other frameworks such as Angular and React.
Community comments
Dart programmers will be happy to use it.
by Andrew Mezoni,
Re: Dart programmers will be happy to use it.
by William Smith,
Re: Dart programmers will be happy to use it.
by Andrew Mezoni,
Dart programmers will be happy to use it.
by Andrew Mezoni,
Your message is awaiting moderation. Thank you for participating in the discussion.
However, this will be possible not immediately.
First, Typescript programmers should implement definitions on DefinitelyTyped.
And only after that the Dart enthusiasts will be able to adapt these Typescript definitions to the Dart language.
I think this way is much better than nothing (or waiting when enthusiasts will write a good Dart wrapper).
Re: Dart programmers will be happy to use it.
by William Smith,
Your message is awaiting moderation. Thank you for participating in the discussion.
Do you think Dart has any sort of future? As far as I can tell even Google has abandoned it.
Re: Dart programmers will be happy to use it.
by Andrew Mezoni,
Your message is awaiting moderation. Thank you for participating in the discussion.
>> Do you think Dart has any sort of future? As far as I can tell even Google has abandoned it.
Google engineers did very unfair to those programmers who have been involved in testing their software (called Dart Web Platform).
Google engineers have chosen a "bleeding edge" technology for Dart and as payment for testing, Google has offered a variety of features (in the form of numerous promises, large and small, official and those that were given publicly by developers routinely).
Most of these promises was never implemented into practice by the Google engineers.
Previously, Google engineers did not hesitate to promise, but now they behave very reserved, not to exacerbate the discontent of those whom they had been deceived.
But in fact they are very much not made out of what they promised.
Now, almost any criticism ignored and condemned by the Google.
This is because Google have no other choice, because many projects have already been abandoned and no longer Dart is developed as community wants, when compared with other similar, but popular software.
I even can say that Dart community no longer plays an important role in development. However, it has always been.
But at the beginning of the development the Google trying to pretend that the community is a very important part, now it is not a fact.