I think the article leaves a bit of a blind spot where the dreaded "in-house framework" lives. Those are always the worst of frameworks when evaluated like you

I think the article leaves a bit of a blind spot where the dreaded "in-house framework" lives. Those are always the worst of frameworks when evaluated like you would evaluate a "proper" framework, but they can make up a lot by being used exclusively by their original authors or at least under their personal supervision (then it all depends on people skills). The biggest drawback is that they can cut you off from a lot of upstream innovation, so maybe don't go that way in client side front-end dev... (but sometimes even that can be good, a properly fossilized pure servlet source tree can be nicer to work with than one that has gone through every hype since struts2)