Agreed, Svelte is by far the most productive FE I’ve used. Coming from a jQuery/templating background, at first felt Vue was the most intuitive to use (React felt alien, Angular overly verbose)…
Until I met Svelte…Vue, minus the BS. A clean template system, less boilerplate, no Virtual DOM, nice Typescript support, intuitive state mgmt.
Btw if you liked Polymer 2.0/3.0 you may also like Lit (formerly lit-element)[0].
It has a less "proven" ecosystem around state/async action management and some other concerns (i.e. there's no redux/vuex), but the controller paradigm[1] looks pretty fresh and interesting. I'm of the belief that most of the time doing an async request or two and some caching and good architecture is enough for most app (not everyone needs the flux pattern).
Lit is by the best implementation and standards-compliant component-centric library IMO. Tried a bunch of them back when I was trying to figure out if there's a better way to handle state in a component-centric world[3].
Fake it til you make it. The game is all about perception/value. If you have a higher perceived value than actual value it plays to your benefit.
You really need to turn around the interview on the interviewer. Best means of accomplishing this is to run through the technical evaluation as quick as possible, then turn the question around in terms of whether it would solve their current problems with what they're working on. It likely won't, so try to identify current problems within the organization/team/project. Dig into those problems and help identify solutions. Question the tradeoffs with the existing system and their current approach.
