re: Why You Shouldn't Use A Web Framework VIEW POST


Can you point me to some GitHub repo which implements things this way??

I believe that framework lead you to violate your own separation rules and make you mess with dependencies, resulting in a high coupled code, hard to change.

But solution could be programming the logic outside of the framework and then make the framework use your logic.
Instead of getting rid of the framework which takes care about low level details that you don’t want to deal with on daily basis.
Such as security caching asset serving routing

code of conduct - report abuse