Echoing the same here. I just found Vue a few days ago. Instead of starting with the documented way on their site, I'm going the Typescript with Components route, so I have classes, and typing. Now if I compare all of the frameworks I've been learning lately. Ang2 has a horrible module system that just gets in the way and confuses the crap out of everyone. Vue with Typescript is basically Ang2 without that horrible module system. React's flux model still bothers the crap out of me. Polymer's not on NPM and refuses to see that as the way to win.

Polymer's got the BEST router system however. It makes the URL choppable at the component level, not the app level. So you can literally throw in an external component and it can add it's OWN part of the overall URL. I don't know any other framework that can let an external component eat some of the URL if it needs to.

For the record, we do not refuse to see npm as the "best way to win", we just have work to do to get there without abandoning out current users. We are currently working on npm support, and have kept the github issue up-to-date with developments.

Same with React. Tiny API, not much concepts.

Even Cycle.js just has a few concepts and is even more flexible than React or Vue.

Angular 1&2 feels like someone let loose a Java or C# dev onto JavaScript, who tried to apply all the design patterns™

I feel Vue is simpler and faster as far as programming is concerned as compared with React.

yes, it's more OOP like the others. which is probably easier to understand for most devs.

But I'm currently buying into the FP fad, haha

Given that FP has been around longer than OO, I'm not sure it qualifies as a fad!

:-D I am not in any fad as such, but for some reason I find writing functions better than writing classes, it is faster and more intuitive to write vue-js code than react code. Simple architecture and small API.

Funny you should say that since the other person was implying that React apps are usually functional(largely when paired with Redux).

Many think about separation of concerns when splitting up CSS, HTML and JS, but what they are doing is separation of technologies instead.

No, what we are doing is separation of concerns. CSS, HTML and Javascript aren't just separate technologies, they're completely separate and unrelated concepts.

HTML is content. CSS is style. Javascript is shit.

I am enjoying VueJS also and it is the 1st framework I've developed in since starting dev. I measure my skills on how comfortable I am doing whatever it is I am doing. I have to say that I've enjoyed Vue thus far, but I don't have any other framework to compare it to. I also have to say that the Front-End Developer Handbook 2017 looks pretty sweet for anyone in front-end dev right now. But again, I'm only an adolescent at this, what do I know?!?! :)

Me too, the first JS franework, I am writing an easy to ubderstand tutorial for VueJS, would you be interested?

Thanks for the offer, but my plate is full right now, sorry.

When I started looking at frontend frameworks a couple years ago, I ended up with Vue as well. Just enough functionality for the majority of tasks. Angular was waaaaaaay too complex for most needs. Simple two way data binding is where it's at.