The Vue Point

Vue. 'The Vue.js patreon campaign now has over $8,000 monthly pledge from the community and sponsors. It is absolutely amazing to be able to work full-time on an open source project that I am genuinely passionate about, and for that I am forever grateful to all the supporters.' [1] https://medium.com/the-vue-point/the-state-of-vue-1655e10a340a#.f23h1k…

The benchmarks[1] make me intrigued, along with the perceived ease of use. It seems well maintained as well, but I think that Angular or React will get a bunch of these improvements, given the sheer amount of contributors they have, and that they are backed by large companies. The blog post[1] in general is quite intriguing, recommend giving it a read. [1] https://medium.com/the-vue-point/vue-2-0-is-here-ef1f26acf4b8

What changes are you talking about? Are you aware that Single File Components won't be removed? Asking because a lot of people on Twitter and Reddit seem to be under this impression that it's going away... If you're talking about changing from the current v2 object syntax to v3 composition api might be hard indeed, then I agree with you... but I'm hoping we'll get some compatibility layer soon enough. EDIT: According to Evan we'll get a "compat build" in the RC phase [1] [1] https://medium.com/the-vue-point/plans-for-the-next-iteration-of-vue-j…

lhorie and smuemd, thank you for the additional detail, but as a non-Mithril user I still don't understand the big picture. For example, Vue 2.0's announcement[1] made clear that the release was about performance, new render functions enabling new component-based patterns, and server-side rendering. What's going to "wow" Vue and React users who haven't looked at Mithril? [1] https://medium.com/the-vue-point/vue-2-0-is-here-ef1f26acf4b8

It seems like a distant dream where Evan You promised 99% syntax backwards compatibility: https://medium.com/the-vue-point/plans-for-the-next-iteration-of-vue-j… About a year ago, my team rebuilt a large solar power plant prediction modeling Angular 1 application with Vue.js 2.0. It was the only big bang rewrite I've heard of that was a massive success. I work in Vue.js everyday and swear by it. Mr. Evan You, don't do this to us.

Vue 3.0 is reported to support class-baed components natively: https://medium.com/the-vue-point/plans-for-the-next-iteration-of-vue-j…

Here is one more success story nowadays about Vue.js and Evan You (creator) - https://medium.com/the-vue-point/vue-in-2016-8df71d98bfb3#9af5 > Going Independent > In early March I decided to work on Vue full-time independently and started a Patreon campaign, which has been (to my surprise) quite successful so far. It is my first time working independently without having to report to a manager, and it has been a very liberating experience. They also use OpenCollective: https://medium.com/the-vue-point/vue-is-now-on-opencollective-1ef89ca1…

https://medium.com/the-vue-point/the-state-of-vue-1655e10a340a Doesn't say anything about being sponsored by Alibaba, but Evan does indicate adoption there.

It's in the works: > "Native Rendering The collaboration with Alibaba’s Weex project has made some substantial progress. Our first major goal — making Vue 2 the actual JavaScript runtime framework on top of Weex’s native rendering engine — has been completed in the latest 0.9.4 release. In 2017 there will be revamped documentations, better onboarding experience and API improvements based on feedback from the community and large-scale production use at Alibaba." https://medium.com/the-vue-point/vue-in-2016-8df71d98bfb3#.uzzbgq7wj

Is there more work to be done besides the reference made in this announcement? > vue core, vue-router and vuex 2.0 all have TypeScript typings shipped in the npm packages https://medium.com/the-vue-point/vue-2-0-is-here-ef1f26acf4b8

Technically not yet, but from the official Vue 2.0 release announcement: > we have started an official collaboration to make Vue 2.0 the actual JavaScript runtime framework for Weex. This will enable users to write universal Vue components that can be reused across Web, iOS and Android! The collaboration is still in early stages, but it will be a big focus for us now that 2.0 is out, so stay tuned! https://medium.com/the-vue-point/vue-2-0-is-here-ef1f26acf4b8#.omtcwhy…

Announcement at Medium: https://medium.com/the-vue-point/vue-2-0-is-here-ef1f26acf4b8

Also nice article on Vue.js 2.0 https://medium.com/the-vue-point/vue-2-0-is-here-ef1f26acf4b8#.rgh0t4w…

IE 11 is the last browser with any substantial share that is no longer being actively developed (and automatically updated). As such the are a number of new features that get broad support in "evergreen" browsers that IE will never support. Most frameworks and developers end up bending over backwards to polyfill these features leading to more complex code and larger file sizes. Here are a few examples: ES6/ES2015 - https://caniuse.com/#search=ES6 Every other major browser supports this natively aside from IE, but most people still transpile their modern code down to ES5 + polyfills for compatibility CSS Variables - https://caniuse.com/#feat=css-variables Again, widely supported, but instead we use tools like SASS/LESS Web Components[1] (Shadow DOM[2] and Custom Elements[3]) Newer frameworks like Ionic 4 rely heavily and web components and see it as the future of all UI frameworks and the end of framework churn[4]. Once again IE 11 holds back the pack and has to be pollyfilled[5] 1. https://developer.mozilla.org/en-US/docs/Web/Web_Components 2. https://caniuse.com/#feat=shadowdomv1 3. https://caniuse.com/#feat=custom-elementsv1 4. https://blog.ionicframework.com/the-end-of-framework-churn/ 5. https://blog.ionicframework.com/october-2018-a-big-month-for-web-compo… Proxy - https://caniuse.com/#feat=proxy Vuejs is completely rewriting its observation mechanism[6] to be proxy-based in version 3, however it appears that cannot be polyfilled and so they will be…