3 ms·

Frameworks are the wrong way to solve many problems at once. Frameworks are a disease. An example of something that solves lots of problems at once well: a lan

• ebiester 16y ago
  Sometimes yes, sometimes no. A framework makes a lot of sense for internal applications and large companies. You're often repeating a very similar application over and over (same style, same database, same replace-unwieldy-Excel/Access power user DB problem.) A framework makes a lot of sense for consulting-ware. Deploying 20 versions of a highly customized application with a lot of reuse. As I see it, this is the use case for Spring. I can't think of another way to easily test such a system. Frameworks make sense when you need to assemble a team together quickly to solve a problem. You are inheriting a set of best practices that allow a quicker norming phase. Frameworks make sense when you have average and junior programmers as the primary workhorses on a project. (Note: we don't have enough A-listers to solve all of the world's computing problems.) Frameworks aren't for every problem. That doesn't make them useless.
• ToastOpt 16y ago
  > a language and its compiler/interpreter I heard "high-level program translation framework".