My takeaway from this article is don't use bizarre Java web frameworks that force you to configure everything through boilerplate xml files that you end up havi

My takeaway from this article is don't use bizarre Java web frameworks that force you to configure everything through boilerplate xml files that you end up having to constantly change. No clear argument is presented against why I shouldn't use a web framework that helps me avoid writing the same bullshit over and over again to deal with: - user accounts, permissions, password resets - general admin panels - form validation, csrf protection - sessions, 'flash' messages - pagination - image uploads, resizing, thumbnailing - internationalization One might argue that the downfall of some web frameworks are their lack of flexibility when you need to move beyond the out of the box solutions. But honestly the only thing I get out of that article is don't write web apps in Java when there are much better tools for the job.