3 ms·

If you aren't using a framework, you are writing your own framework. Moving from project to project will be a pain, for you and others. Disliking frameworks is

• js8 10y ago
  You can also write a library, which is a different thing than framework. What you're saying is a false dichotomy, based on different understanding of the term "framework". I think what mainly distinguishes framework and library is that framework dictates you conventions outside its own code, where library does not. This dictate can be as simple as "I must be in charge of running the program, i.e. the top-level thing". See, the conventions are not bad per se, however, they do not compose. So bundling conventions with potentially reusable code, as frameworks do it, is a wrong idea.
• augustl 10y ago
  In my experience, I've been able to completely avoid the framework, rather than building my own. I end up with pretty much the same controller and db access code, absolutely no implicit logic, a "main" entry point (in my case typically in the form of a @ServletContextListener class), and maybe 100-150 lines of boilerplate - i.e. the stuff that is usually implicit, such as reading config files, connecting to a database, etc.