Hacker News Reader

I think in many cases a good minimalist framework will get a core set of functions out of the way (in web for example: routing, autoloading, dependency injection, etc.). Grabbing something small that provides a proven but efficient backbone can let you focus on delivering core value, but then can easily be switched out later as the solution grows.

View on HN

One would think that you wouldn't want to switch out a framework later. After all, your choice of network is one of the defining factors of how everything will work. Swapping it out means rewriting most, if not all, of your CRUD functionality and then doing a whole lot of regression testing. Doesn't seem very cost or time-effective.

Regression testing is inevitable, but with a minimal framework, you'll essentially end up rewriting the controllers, and part of the views. If you switch templating systems, modifying the views can't be helped. And the controllers should only be a glue between your view and the service layer, so it ought to be solely administrative code.

Reply on news.ycombinator.com