Live data from Hacker News

Vue 2.0 is here

medium.com

41–50 of 73 posts

Re: Vue 2.0 is here

#41
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)

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.

Do you think Vue.js has a chance? I hope it does

Re: Vue 2.0 is here

#42

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). (edit: typo)

>We disliked the standard starter project with Webpack and its idioms, with un-inspectionable compiled javascript source code

The template generates source maps.

Re: Vue 2.0 is here

#43
I regularly loathe Javascript. I'm familiar enough jQuery to get by and enough Javascript to drive business value.

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.

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.

Re: Vue 2.0 is here

#46

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) 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. Do you think Vue.js has a chance? I hope it does

Actually got in argument with someone last week in defending his company's selection of Angular (which I've used) "you never get fired for choosing Google." Well I'm old enough to remember 'you never get fired for buying IBM.

My philosophy is you move ahead by choosing the best product and currently imho Vue is best. But then again having tasted the freedom of being an entrepreneur I couldn't ever work again in the big company environment.

Re: Vue 2.0 is here

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

When we were deciding between a few other frameworks, the choice was very easy.

Re: Vue 2.0 is here

#49

Vue deserves quite a bit of attention. 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. 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, o…

VueJS has what I liked in Angular 1.x (html-enhancement, directives) and also in React (building reusable components). Having built projects with both, I quickly felt at home with VueJS. It definitely deserves its place in my toolbox, and I'm definitely going to check that v2.0.

btw, my 1st VueJS website that my webagency launched 1 month ago: http://lamegapromodesgrandesmarques.com

Re: Vue 2.0 is here

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

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

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.

Post reply on HN