Seriously, I don't. I do embedded and Windows desktop development in what is essentially a process control environment. The closest I get to web development is using HTML to display static report data.
...depending on how you want to look at your html reports.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
At work I use Angular and ExtJS. Both create incredible unnecessary bloat.
I honestly can't see the need to even use TypeScript, and if you look at some of the bizarre, inane, WTF features they're adding[^], I don't want to use it.
I looked at ember, angular ... etc. and coming from a win forms background with no web experience I found them to convoluted and difficult to "get" then I came across vuejs which I found dead simple to learn in comparison while at the same time being powerful and fast, and I fell in love with it.
You can do as little as you need with vue in a page or go all out on it with the vue component files (bundled html, js, css) which is great (I have switched to parcel as my packager instead of webpack which requires no configuration [upgrading webpack to the latest broke my build and I just gave up on it]).
At the moment I'm doing single page apps which are pretty complex and I have found nothing which vue can't handle even with my unorthodox win forms mentality (see TorpedoSync's[^] UI for example).