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.

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 sooo much cleaner.

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 just bought the course myself, at that price it seems like a useful resource even if you only have a cursory interest in Vue.

https://www.udemy.com/vuejs-2-the-complete-guide/

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.

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?

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 http://riotjs.com/release-notes/ . Here is a quick introduction http://vitomd.com/blog/coding/hello-riot-js-quick-tutorial-a... I highly recommend it.

> http://mithril.js.org/comparison.html

> 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.

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.

Vue looks really appealing on the simplicity and completeness side.

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.

Is this looking a lot like Angular 1.x to anyone else? I've heard it's actually more similar to React but I'm not seeing it... ?

Pleasure to work in Vue.js framework. Very easy learning curve. Simplicity is the biggest strength of this framework.

I have created few tutorials on Vue.js.

https://m.youtube.com/playlist?list=PLJ6Y8JfXAV-8_2lHNgP1DhC...

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).

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.

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".

[1] https://github.com/Akryum/meteor-vue-component

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...

Before 2.0:

new Vue({ el: "#el", data: someData, events: { myevent: function(){} } });

after 2.0 :

vm.$on('myevent', function () {})

I found this guy creating a todo app using all popular js frameworks

https://github.com/tastejs/todomvc/tree/master/examples

including vue.js riot.js react, meteor, angular 1,2 dojo, duel, ember, jquery ....

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.

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.

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".

Does this version have a routing guide and production ready routing solution? That's pretty important.

Are there any migration guides from jQuery to Vue which are noteworthy?

I have some projects in Mithril - is it worth it port to Vue?

I can't speak to Vue, but React is overkill for many sites. The virtual DOM etc is incredibly useful for sites that update the page very frequently, but if the only thing you're making is a static site and a contact form, you don't need React.

That said, I do like the React model of creating components (and suspect this is why so many people use it when it's unnecessary). I'm looking forward to browsers implementing custom elements so that we can all compinentise this way without the overhead of a large JS framework.

Not in websites per-se, but even the simplest contact/enquiry web form/wizard with some validation/interaction is a breeze to program in Vue.js compared to jQuery.

We have multiple internal enterprise applications where both jQuery and Vue.js are available. More often than not, when there's a pull request, even for the simplest UI interaction, it can be refactored to few lines in Vue.js from the jQuery event and DOM mess. We plan to move away from jQuery in a year or so, and no new jQuery plugins are allowed.

Vue.js has also allowed us to iterate much faster on complex UI than it would be possible with jQuery.

For bigger apps, you can add components, and for even bigger - add Vuex. Vue.js (same as React) really is the new jQuery.

From personal experience for general web-sites like blogs, etc. it's better to do them old way, you don't need to worry much about seo, caching, precompilation, etc. But business apps huge community-like ones, and big shops benefit a lot from frameworks like that. But you should always base your decision on cost of implementation, support, etc.

Both Vue.js and React allow you render HTML on the server side. This helps get the first render out quickly where the browser can pick up the state and continue from there.

https://vuejs.org/v2/guide/ssr.html

As it usually is in this industry, the answer to this question is: "it depends".

There's a point, where using jQuery alone just won't cut it.

I guess a rule of thumb here would be: If you're providing a service that requires an account - you probably need something more than jQuery.

In vue.js, SEO is taken care of with with server side rendering[1].

This assumes that you are using node.js as your backend though.

[1] https://vuejs.org/v2/guide/ssr.html#SEO

What I like about Vue is that it makes it is very easy to use it as a component of a larger website or non-SPA application. You can use it where you would otherwise use jQuery in order to build widgets or interactive components. It makes it very easy to drop it into a page without a lot of ceremony (no flavor of the month build tools or exotic precompilers are required to get started).

In the past I've used https://prerender.io/ with a Backbone + Marionette website. You configure your .htaccess (or similar) to direct web crawler's to prerender.io's cached representation of your website. Works great and completely side-steps the issue of SEO for dynamic websites.

Google will index sites that render their pages through Javascript. There are two caveats to be aware of:

1. It drops out if it takes more than 5 seconds to complete its operation and uses whatever is render then.

2. Indexing with HTML happens in near-realtime. Indexing with JS to HTML is delayed by about 1-5 days depending on the popularity of the site.

So if you're serious about it; you ought to heavily include metadata for Google to index during the first run through or place a bare bones HTML copy down.

I can't find the article yet, but a few months ago I read that only some chinese search engines had problems with that. The big ones didn't care much.

It's like Angular in that they use a similar templating language, and it's like React in that they're using a component-based declarative DOM API.

here's an link[0] to a comparison with react, angular 1 and others.

[0] - https://vuejs.org/v2/guide/comparison.html

They openly talk about how they took what was successful in those platforms (React and Angular) and others, then built Vue with that in mind. Plus their goal from what I've heard was to also remove what other platforms did poorly (benefiting from hindsight) and hopefully do those things better by learning from their mistakes.

Nothing about how they said this was done in a manner that was boisterous, just simply leveraging what has been learned from first movers and now they are hoping to pull their own Apple, by making a better product as second (or third or fourth.....) movers in the market. ;)

it uses virtual dom to render and components https://vuejs.org/v2/guide/comparison.html

It's more that many many frameworks imitate Handlebars, or accept that Handlebars is good enough and it's not worth inventing new syntax.

If it's your opinion, as it is mine, that HTML frameworks should deal with HTML, instead of abstracting it away, then this isn't a bad thing.

Yes, the tag names are even similar but the performance and simplicity is even better than ng2.

You can use it for a page that isn't a SPA for example.

Angular2 has a huge surface area, conceptually. You might need that surface area. But it's daunting. Angular2 also expects you to teleport into a very modern future of tooling and development practices. That said, it's a safe choice...everything you might want to do has been done and complained about on StackOverflow. [wink]

You may want to check out Aurelia too. One of Angulars main devs left the Angular Team because of its direction and build Aurelia the way Angular should have been.

I played with it a bit and what's awesome about it that you just write plain JS most of the time. No weird stuff like JSX and whatever. Docs arn't that great tho

Well, it might help if you said why you're looking to move from Angular 1. What problems do you have with it? How many developers are working on the project? Do you use libraries like angular-material? ...

There are a thousand factors why you'd chose one above the other. I would just be very wary of comments like: "Definitely framework X".

Angular 2, not worth it. We made our decision to migrate an old Angular 1 app to Vue.js. Best decision ever.

The upgrade adapter isn't ready for primetime yet from what I gathered.

Can't speak for Vue, but Angular 2 is pretty nice, and the performance benefits are significant. There are some complexities, mainly around AoT compilation, but those are challenges that one would come across if one wanted that anyway.