For folks who haven't tried Vue yet, I just completed my first project with it and I'm really excited about using it more.<p>Specifically, I used learning Vue as an opportunity to upgrade a simple jQuery-based SPA (with a PHP backend) to ES6, JS modules and Vue. It was a little hairy to bite off all of that stuff at once, but the Vue community was really helpful. In contrast to more monolithic frameworks I didn't have to port everything at once, and the re-implementation of the bits I did port are <i>sooo</i> much cleaner.<p>FWIW, there's a highly-rated Vue.js 2/Vuex Udemy course on sale for an impulse price of $14 (normally $190) as I type this. With the caveat that I <i>just</i> bought the course myself, at that price it seems like a useful resource even if you only have a cursory interest in Vue.<p><a href="https://www.udemy.com/vuejs-2-the-complete-guide/" rel="nofollow">https://www.udemy.com/vuejs-2-the-complete-guide/</a>
So far my Vue.js experience has been great. Even though I don't particularly enjoy front-end development and the tools and techniques I'm supposed to use for them, Vue.js has been a breath of fresh air between my frustrations with HTML, Javascript, npm, CSS, HTTP and all the other things that are needed to stitch everything together. It really is a great framework.<p>The one thing that does still bug me these days is that even now that Vue 2.1 is out, many components I'd like to use are still not compatible with Vue 2.x, and almost all the Vue tutorials, questions, solutions, etc. I find are about Vue 1.x, which is mostly incompatible with Vue 2.x. But that should improve over time, of course.
I am sorry if this sounds too ignorant, are frameworks like Vue.js (I actually read the guide and understood some wonderful things about its philosophy since I am actually developing backend mainly) or React, etc.. reasonable to use in websites in general (instead of jquery or taking some tasks from it) or they actually only reasonable for mobile web applications and SPAs?<p>What about the SEO and search engine rendering to custom HTML elements like in Vue.js components? is it okay or affects SEO?
I don´t know why Riot.js (another js framework) don't attract more people. I used it and it´s awesome. Today they launched the 3.0.0 version <a href="http://riotjs.com/release-notes/" rel="nofollow">http://riotjs.com/release-notes/</a> . Here is a quick introduction <a href="http://vitomd.com/blog/coding/hello-riot-js-quick-tutorial-about-this-awesome-lib/" rel="nofollow">http://vitomd.com/blog/coding/hello-riot-js-quick-tutorial-a...</a> I highly recommend it.
> <a href="http://mithril.js.org/comparison.html" rel="nofollow">http://mithril.js.org/comparison.html</a><p>> Vue's implementation cleverly hijacks array methods, but it should be noted that Javascript Arrays cannot be truly subclassed and as such, Vue suffers from abstraction leaks.<p>Can anyone who knows how vue is implemented explain this statement?
I've been using Vue.js for a new project and it is a breath of fresh air after using React. It has all the benefits of Knockoutjs (which was my gateway into these types of frameworks), but much nicer in-code organization (I'm looking at you ko.observable).
I am always looking for the fastest way to build a complete app. Brought me to Rails. Then to Meteor/React (which was mixed). Then some Rails/React which is ok.<p>Vue looks really appealing on the simplicity and completeness side.<p>I would like to know from people using Vue what backends you're using. In order to complete the loop - the simplest stack overall Vue+???.
Nice, I love Vue.js it is light weight yet fulfill 90% of the needs of a large SPA without a third party language, some bureaucratic dependency injection and without getting in the developer's way by mandating this or that build tool. But competition is good so I'm glad there is a front end framework for everyone out there.
I'm going to build a vuejs markdown site editor similar to Gatsby I just don't like Facebook it's refreshing that an independent project is gaining popularity the server side rendering is a big deal when you want to support mobile well.
Pleasure to work in Vue.js framework. Very easy learning curve. Simplicity is the biggest strength of this framework.<p>I have created few tutorials on Vue.js.<p><a href="https://m.youtube.com/playlist?list=PLJ6Y8JfXAV-8_2lHNgP1DhCwvB6le3rty" rel="nofollow">https://m.youtube.com/playlist?list=PLJ6Y8JfXAV-8_2lHNgP1DhC...</a>
So glad this project is gaining more and more traction. Been using it since very early releases, when I was sick of dealing with overly complex front end libraries.
I'm really excited about the scoped slots feature. Finally it's really easy to create components that can be customized by the user from the outside. For example, it's now really easy to create a data table (with features like filters and sort), and with each row showing not only the data text, but also any other feature you might want to embed in it (like attach click listeners to each row, or popup some menu on hover).<p>I believe there was a way (probably a complicated hacky way) to achieve this previously too, but I never investigated it too much. Now it's really easy.<p>Kudos to the Vue team for this release!
In case someone user Meteor - Vue plays very nice with Meteor and there exists a great integration package [1], which means if you're familiar with Meteor you can write full stack applications with it very easily and quickly with it. The package supports hot module replacement out-of-the-box. It's also dead simple to start using it, if you already have Meteor installed it's a matter of running "npm install" and "meteor".<p>[1] <a href="https://github.com/Akryum/meteor-vue-component" rel="nofollow">https://github.com/Akryum/meteor-vue-component</a>
I'm looking to move a few projects from Angular 1. What do developers think of migrating to Angular 2 vs Vue for this? I've played with Angular 2 but can't shake the feeling that it's overly complex.
I still wonder why they moved the events from the constructor to the instance...<p>Before 2.0:<p>new Vue({
el: "#el",
data: someData,
events: {
myevent: function(){}
}
});<p>after 2.0 :<p>vm.$on('myevent', function () {})
I found this guy creating a todo app using all popular js frameworks<p><a href="https://github.com/tastejs/todomvc/tree/master/examples" rel="nofollow">https://github.com/tastejs/todomvc/tree/master/examples</a><p>including vue.js riot.js react, meteor, angular 1,2 dojo, duel, ember, jquery ....<p>it's a great way to compare frameworks
I really miss 1.0's inline way of writing javascript anywhere inside the dom (attributes) via {{ execute_raw_js_code() }} as well as the ability to run filters on it. Is there anyway to get them back on Vue 2? I have to admit, this was a major step back for me when upgrading to Vue 2 from Vue 1.<p>I also really loved the Vue 1's way of handling transitions. Now having them inside it's own wrapper really diminishes the elegance I felt from Vue 1.<p>Wish there was some ways to get them back instead of having to downgrade.
I'm currently using (and enjoying) my first Vue project. I have to say the camelcase support for JSX events feels like a step backwards. The `on-` prefix had a nice semantic way of telling you that thing is an event (either DOM or $emit from component). Now there's just this implicit `onFoo` which could be an event, or could be a prop, maybe component will invoke it directly like in React, maybe it will $emit, who knows?
I've been waiting for scoped slots for so long. I've implemented several workarounds since I started using Vue a year ago. Creating a directive to pre-compile a slot template in the child scope in Vue 1, and then once Vue 2 rolled around, making lots of functional components and passing them around. So glad they finally added this.
I've been a long time React and Angular user, but is still sick to implement correctly enough SSR for my projects. And VueJS just did it elegantly ! I must say, thank all React + Angular folks as the pioneer for better CHANGES. This is THE time for us to change. Really.
I tried to use Vue 2 for a pet project but couldn't get the routing to work. It seems the router was lagging behind in versions and there were no guides on "router 2.0".<p>Does this version have a routing guide and production ready routing solution? That's pretty important.