21–30 of 73 posts
Always good to see frameworks not built by big companies thrive.
For someone wanting to learn modern javascript, it's so hard to know where to start. So many different frameworks to pick from. There doesn't seem to be much point asking for suggestions either, as everyone has a different opinion on what's best.
If I had a recommendation, it would be to just stick to one for a little while, and then once you're comfortable, branch out and try to 'optimize your opinion'.
edit: and I wouldn't recommend any specific one. If it's the first one you ever learn, and aren't building any serious projects with it, honestly choose whatever the hell you want.
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.
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.
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.
While it shares some similarities with Angular 1 semantically, Vue.js is at its core extremely different. The framework is very light and entirely component based, meaning that the concept of DOM elements as directives and controllers goes away. It also does away with dirty checking so you can use Object.defineProperty to set up read-only array values, something that was causing us to run into infinite digest loops in Angular.
There are lots of other differences but in general, the transition from Angular 1 to Vue.js was relatively painless. There's a small learning curve when getting used to the data-binding through getters and setters but once it clicks it's smooth sailing. Hope this has been helpful.
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…
React...databinding? huh?
Vue.js is by far the sanest framework available for JS, period. It has excellent docs, it is intuitive, well written and well maintained. 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. With that said, after working on a fairly…
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.
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. 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 by far the sanest framework available for JS, period. It has excellent docs, it is intuitive, well written and well maintained. 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. With that said, after working on a fairly…
What's the alternative?