I think it's better to ignore the world of framework hype and just code to the browser APIs as described by the standards. You can basically guarantee that your

I think it's better to ignore the world of framework hype and just code to the browser APIs as described by the standards. You can basically guarantee that your site will still work ten years from now and that your knowledge will still be relevant (though you'll need to keep up to date with new features e.g. flexbox). I personally find it more work to learn frameworks and deal with the leaky abstractions inherent in them than to work with the browser directly. Especially when I hit a case where I want to do something that the framework authors didn't cater for and I end up having to go down to the browser APIs to implement it anyway. In the short term, it's a bigger investment to learn the underlying technologies, but in the long term it pays off big time, since you don't end up being stuck with something that sounded great two years ago when you started your project but is no longer maintained.