

re: I haven't. Give them a go if you have the time and let us know. It's been about 1.5 years since I used polymer, and I haven't missed it one bit. B...

I still need to learn some stuff before doing that. I'm trying to check by myself if I can get rid of frameworks and use only html CSS JS for my little personal projects. I still need to know how to make a router and spa without framework, how is it to do a loop like ng-for/v-for in pure JS and if it's worth it, and check the compilation with npm babel etc without the great vue cli 3.
PS: I'm a UI developer, not that much of a front end engineer

I've heard some really good things about svelte too, and it might be easier to get into, considering that, like vue, you can integrate it piecemeal with your existing html. It's definitely something to keep on the radar.

Isn't it another framework or library we could avoid?

my opinion is that we shouldn't be simply looking to avoid frameworks (:

if you just need the smallest amount of logic (or none at all) in your web page, then sure, vanilla js, or nothing, is good.

but if you're looking for some kind of updating component which does stuff, I don't want to (personally) do the heavy-lifting that a lot of other talented people have done before me -- in this case, I want to use a framework so that I can concentrate on my application logic, not re-inventing the wheel (and dealing with cross-browser issues)

I'm advocating that people use the tooling which works for them -- don't use a framework just because it's "cool" or someone said you should. Don't ditch your framework because someone else said theirs is better, unless theirs actually does work better for you. Best of all (coming back to the OP), don't propagate the FUD that web components are a "standard", when they are just another framework, unratified by the W3C, pushed by Google. Do you remember the debacle last year when Mozilla complained about anti-competitive behavior where YouTube was signifigcantly slower in Firefox? That wasn't Google outright throttling YouTube for Firefox users -- that was Google assuming that they're too big to fail, baking their framework into Chrome and releasing a new YouTube using their framework, probably hoping that it would drive up the desire to make web components a standard.

Anyways, like I say, I don't have appreciable react experience, but if you're getting stuff done with AngularJS/Angular, Vue, Polymer, Svelte, whatever (I've also used a couple others, including CanJS for a prod site and a few others I've dabbled in, including Knockout and Ember), then carry on getting stuff done. If your framework is working for you -- use it (:
My suggestions are based on my experience:

  • Polymer gets unwieldy on larger projects
  • AngularJS is good, but not for monstrous forms (ie, think spreadsheets)
  • Angular is good, but requires full buy-in and some deep knowlege out the gate
  • React seems to work well for others, but requires a large mindshift, which may be worth it -- I don't have enough xp to tell
  • Ember rubbed me up the wrong way with opinions like "AMD is WRONG"
  • CanJS -- not sure if it's even maintained any more?
  • JQueryUI -- good in a quick-fix situation (also, check out Chosen for drop-downs)
  • Knockout has never been a positive experience for me
  • Vue -- easy to pick up, can be brought in as needed or as a complete framework, with vanilla JS or TypeScript, lots of freedom, and we've built a white-labelled online application with it, with > 2000 tests, so it's quite capable for large things, but easy to shim in for small uses
  • Svelte -- apparently has much of the same wins as Vue (after listening to a podcast by the creator), though I haven't used it, so again, YMMV
  • Vanilla JS: good for smaller things, but you have to do all the heavy-lifting yourself, including dealing with cross-browser issues

/2c (:

Thanks for your answer.
OK so I'm going to check out the web components world and see if I can switch to something different or continue with Vue (I love Vue, it reminds me of the JQuery days, lots of freedom)

Good idea -- that's the only way to form solid, useful opinions about frameworks: build with them, see what works and what doesn't, what's easy and what's hard, what's a pleasure and what's a real pain.

Personally, if I were about to build something new, I'd pick Vue if the project Really Mattered or if I didn't have time to experiment, otherwise I'd like to give svelte a crack (:

code of conduct - report abuse