> home-written framework towards Laravel I would think about that very long. Over the years, experience has shown me that regardless of what framework or libra

> home-written framework towards Laravel I would think about that very long. Over the years, experience has shown me that regardless of what framework or library you use, you introduce a lot of dependencies to your app when you build on such a framework or library. The common sense says that they should make things easier, and at the start they definitely do that. But over the years, you start encountering backwards-incompatible changes, major moves etc in those frameworks and libraries which start taking your time. And sometimes a considerable chunk. I would only use a framework or library that has a major backwards compatibility policy or viewpoint. JSON's 'only add, never deprecate' is a very good ideal to strive to. Even if this couldn't be entirely feasible in software, it should be at least strived to. So I'd say if something that is built in-house works, easy to use and keep maintained, there is absolutely no reason to move to an external framework.