vue

I just went through the whole 'getting started' guide [1], reading everything, looking at the examples, and playing around in my own npm playground to see if I really got it. I still consider myself a novice, I've only spent about 6 hours playing with it, but I'm already able to write my own components, communicate between them using events, set up data model for my app, binding the data model to bootstrap components in my templates, etc. Not bad for someone completely new to web development. Which says a lot more about Vue.js than about my own capabilities ;-) One tip I can give you is to take a very good look at the Vue 1 to Vue 2 changes [2], and all the things that have been deprecated in Vue 2 (quite a lot). The big mistake I made was to mess around with examples written for Vue 1 and thinking there was some problem with the framewor

I see a lot of projects closing down due to lack of time/funds. Why don't more projects take sponsors and display a banner on their readme page. For example Vue.js generates 10k/mo with sponsors: https://github.com/vuejs/vue

yep, Vue has an official support for TypeScript as well: https://github.com/vuejs/vue/tree/dev/types

> {{ data | json }} So neither debugger support nor printf-debugging, you just have to hope you'll be dumping garbage in a place where it can be seen and doesn't break the page entirely? > <li class="for-example" v-repeat="item in list">{{item}}</li> Ignoring that vue changed the name of the directive a while ago[0] that doesn't even remotely work, according to its documentation v-for (née v-repeat) works on native arrays, it's not going to work in any sensible manner on immutable.js structures. [0] https://github.com/vuejs/vue/issues/1200

Vue's "default" way of doing things is plain JavaScript or Babel if you're using the vue-cli templates. However, with Vue 2 TS typings ship with the packages according to the final comment in this: https://github.com/vuejs/vue/issues/478 so I'd assume TS is officially supported.

Thanks, we've updated the link from https://github.com/vuejs/vue/releases/tag/v2.0.0 to this.

You don't need the owner's permission to fork it. It's MIT licensed. https://github.com/vuejs/vue/blob/dev/LICENSE

> Vue version updates are tremendous time sinks. API thrashing was common from the original 0.x.x releases to 1.0.0 I didn't have to endure this, although pre-1.0 API breakage goes with the territory (of pre-1.0 software...). The 2.0 API changes look pretty sane (https://github.com/vuejs/vue/issues/2873); once it is official and the vue-cli webpack template is updated, it looks like only a little work to upgrade. Vue's documentation (in the present) is really good, and was a motivating factor for me choosing it over React.

Here the changelog: https://github.com/vuejs/vue/issues/2873 I love VueJS. I found it very easy, specially when you aren't building a SPA, but want something more powerful than jQuery without being overkill like React.

Our company reviewed many of the options available based of suggestions from our Reddit posts. In the end we made a constructive attempt at trying all the libraries/frameworks that our team could attempt in a single sprint. In the end, we tried React, Ember, Angular 2, Vue, Mithril, Cycle, Preact and Inferno. We tried the latest Vue 2.0 (https://github.com/vuejs/vue/tree/next) and Mithril 1.0 (https://github.com/lhorie/mithril.js) betas and we had some great results from both. We also tried Preact but we had issues with some SVG namespaces not properly being rendered so we gave up. Vue and Mithril enabled us to finally use our example app on our legacy Android testing devices. The experience with Cycle and Angular 2 was about the same as React (unusable) and the latest Ember was better but the initial page load times were still terrible.

I've never used Weex (or React Native) but it looks like Weex uses VueJS syntax to render components [1], just like React Native uses React syntax. [1]: https://github.com/vuejs/vue/issues/2119