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.
Does this "new" hyped framework needs entire libraries and basic components to be ported too?
Nope. It's just web technologies without reinventing anything you don't want to, which is why Vue's motto is "The progressive JavaScript framework", it's got nothing to do with politics :)
If you want componentization of some library you're gonna have to download the bindings, but if not, it's just HTML and you can roll just like you would without any framework. To make an example, I like using Material Design Lite for some cookie-cutter interfaces, and with Vue I simply used it in my templates like I always do. Then I found out about vue-mdl and it helps me cut down on the amount of HTML attributes and such making the thing more readable, so I npm installed it and started replacing things when I touched them and felt like it. But both ways of doing things live together and every bit of it was optional.
Comments
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.
Nope. It's just web technologies without reinventing anything you don't want to, which is why Vue's motto is "The progressive JavaScript framework", it's got nothing to do with politics :)
If you want componentization of some library you're gonna have to download the bindings, but if not, it's just HTML and you can roll just like you would without any framework. To make an example, I like using Material Design Lite for some cookie-cutter interfaces, and with Vue I simply used it in my templates like I always do. Then I found out about vue-mdl and it helps me cut down on the amount of HTML attributes and such making the thing more readable, so I npm installed it and started replacing things when I touched them and felt like it. But both ways of doing things live together and every bit of it was optional.