Just my $0.02... I don't think there's anything wrong with jQuery, and these days it might be a smart choice to lightly augment a website, as opposed to powerin

Just my $0.02... I don't think there's anything wrong with jQuery, and these days it might be a smart choice to lightly augment a website, as opposed to powering a webapp. I've inherited jQuery and Angular codebases on freelance jobs in recent years, and I can say for certain that I'd much rather inherit an Angular project than a jQuery one. You have a fighting chance that the logic will be segregated into the components you would expect, rather than spaghetti markup/js mashups with bits of event handling logic blurted all over the place. That is of course the worst case scenario for a bad jQuery project, but it's often the reality when you step into a messy codebase where a procession of people have hacked around for a short while and then departed. I'm thinking in particular of a situation when a crappy, derelict jQuery plugin had been chucked into the project a while previously, and was triggering "stop script" prompts in certain versions of IE. Fun to debug. It's a framework/library thing. Angular is opinionated, but that's worked in my favour to date.