Vue deserves quite a bit of attention.<p>It's the simplest framework I've found to use in the same style as react (databinding, modules, etc) while still allowing you to use the html/css you've probably already written.<p>This really shines when you want to do something not quite single page appy in your, for instance, bootstrap based site. E.g. a complex web form with some interactivity (autocomplete, add/remove rows, one element affecting another element). This is complex enough to make it a pain to use jquery, but small enough not to want to rewrite the html in a react-compatible way.<p>That use case seems to be the majority case for me which makes Vue my primary tool these days for web front end.<p>Good stuff!
I came across Vue through Laravel and I think they are definitely the best frameworks for their own language (JS and PHP). And the best part is that with the latest versions (2.0 and 5.3) they are working really nice together. Almost as if they were part of the same ecosystem.<p>It's incredible how easy it has become to make a new web app that has everything you need (registration, authentication, api, JWT, notifications,...) with just one command line (laravel new project). It's a huge jumpstart that allows you to focus on what's really important and forget about all the annoying boilerplate.<p>And since Vue.js is so well integrated with Laravel, you get all the benefits of the back-end also on the front-end. With all the authentication and API with JWT (and much more) ready to go, it becomes also a great way for newcomers to learn using Vue and play around with it.<p>These are 2 great videos of Evan You (creator of Vue.js) from Laracon 2016
<a href="https://streamacon.com/video/laracon-us/evan-you-vuejs-workshop" rel="nofollow">https://streamacon.com/video/laracon-us/evan-you-vuejs-works...</a>
<a href="https://streamacon.com/video/laracon-us/evan-you-vue-router-and-vuex" rel="nofollow">https://streamacon.com/video/laracon-us/evan-you-vue-router-...</a>
Vue.js is by far the sanest framework available for JS, period. It has excellent docs, it is intuitive, well written and well maintained.<p>The only real complain that I have about the framework itself is about components. IMO they are the wrong abstraction (they smell suspiciously like objects ) and with their custom .vue extensions, are a pain to work with in my text editor.<p>With that said, after working on a fairly complex Vue app, I won't be writing any Vue apps again. The reason has nothing to do with the framework itself: although it mostly tries to do the right thing, JS just pushes you in the opposite direction every time.
We adopted Vue at GitLab. We couldn't be happier. Our goal was to make frontend development simpler, and that's exactly what happened. Vue isn't strongly opinionated, it just let's you get stuff done faster. You can just use Vue by itself, with solid javascript practices. It doesn't try and "fix" javascript, it just makes things simpler. Evan, you've made an excellent framework. Thank you.<p>When we were deciding between a few other frameworks, the choice was very easy.
Can anyone talk about their experience with Vue as opposed to Angular, Angular 2, and React/Redux? I am fan of Angular 1, but Angular 2 seems to actually just be an inferior version of React/Redux. At first glance Vue seems to be similar in spirit to Angular 1. Is that correct? Any first-hand experiences would be welcome.
I regularly loathe Javascript. I'm familiar enough jQuery to get by and enough Javascript to drive business value.<p>I haven't touched Angular or React or Ember, mostly because of a distaste for Javascript, but also because I/my clients had no need for all the complexity it adds and the little business value it brings. Turbolinks is just fine for me/us/them.<p>But I have played with Vue. I spent a weekend hacking something together and it lives in production today. I'm so incredibly impressed by the library it almost makes me want to play with it more.
Having briefly played with Vue.js before, it always seemed the nicest of the front end frameworks. At least the one that aligned best with the way I like to work (it doesn't get in your way, much)<p>But I fear that the world is too small for 3 front end frameworks, specially when the other 2 are sponsored by Facebook and Google.<p>Do you think Vue.js has a chance? I hope it does
> The official supporting libraries and tools — vue-router, vuex, vue-loader and vueify — have all been updated to support 2.0. vue-cli now scaffolds 2.0-based projects by default.<p>Very nice. Personally, I've been waiting for the vue-cli bit before even thinking about touching 2.0 since I try to avoid trying to build my own JS toolset.
Vue has been my favorite view framework/library/whatever experience in JS thus far. Good docs, sensible supporting libraries, helpful community, easy to understand. Excited for 2.0.
For someone wanting to learn modern javascript, it's so hard to know where to start. So many different frameworks to pick from.<p>There doesn't seem to be much point asking for suggestions either, as everyone has a different opinion on what's best.
Does this "new" hyped framework needs entire libraries and basic components to be ported too? Every 12 months or so I check how the front-end mess is going and last time I tried a few React components and they all needed some compatibility layer with Bootstrap. Or they wouldn't integrate nice with popular stuff I used before, in the jQuery spaghetti times (that's when my front-end knowledged peaked).<p>Do we just throw away everything after a few months? At the time I couldn't find good components or make the entire thing compatible (it's the little bugs that get you), including "basic" stuff like a calendar with date and time, all the bootstrap components, select2. Not to mention proper i18n support. Oh, and it needs to work in every browser (at least the modern ones).<p>If Vue really is a react/angular for toddlers (like me), I hope it wins and that soon there's finally a component set that "just works" and doesn't get rewritten every cycle. I'm talking about components that go beyond the 80% use case. That you can install without thinking twice. That you don't have to worry if it's going to be abandoned next week.
On my job we just picked Vue for a new project, and it's a great experience so far. We disliked the standard starter project with Webpack and its idioms, with un-inspectionable compiled javascript source code, but it was very simple and flexible to create our custom build. It's really a awesome framework, with excelent docs (we were even using the release candidate of version 2.0).<p>(edit: typo)
I hope it has first-class TypeScript support. Having worked in large TS codebase I can't imagine going back to a JS codebase of the same size.<p>Angular has TS and React has Flow, but most of Vue projects seem to use neither. This is fine for small side-projects, but I'm wondering if anyone could share experience building large Vue apps without types.
Vue.js is magic. As I've said before, it's so simple it feels like cheating.<p>But take a look at the docs and the replies on Github issues for the other distinguishing feature - the give-a-sh*t-factor from Evan and the crew shines bright. Just about everything is understandable, purposeful and clear.
I love this framework. I came to it as a back end developer that needed to do some front end work and started off with Angular and then React. I couldn't believe how complicated these two frameworks seemed to be as someone who's done very little JavaScript coding. I then tried Vue and it was so simple, so logical and so productive.<p>What I love about it is that you can mostly intuit what to do to get something to work. It just feels very natural.<p>And the documentation is top notch.<p>I haven't ported to Vue 2.0 yet but I suspect the only issues I'll have will be with third party components built with Vue 1.0
Any good UI component library companion for Vue 2.0 you can recommend ? Something like Keen-UI<p>[1] <a href="https://github.com/JosephusPaye/Keen-UI/" rel="nofollow">https://github.com/JosephusPaye/Keen-UI/</a>
Does vue use vdom diffing? Last time I played with vue, it crawled when having a large number of bindings. Also it's magical data binding doesn't work very well for arrays of arrays.
Also nice article on Vue.js 2.0
<a href="https://medium.com/the-vue-point/vue-2-0-is-here-ef1f26acf4b8#.rgh0t4wmv" rel="nofollow">https://medium.com/the-vue-point/vue-2-0-is-here-ef1f26acf4b...</a>