> Doing something only you understand A simple php endpoint is something any web developer can understand. The more frameworks/libraries/patterns/abstractions

> Doing something only you understand A simple php endpoint is something any web developer can understand. The more frameworks/libraries/patterns/abstractions you throw in the less likely it is they will understand it. Especially years later when the framework is inevitably out of date, good luck convincing why they need to spend money upgrading a framework every year. > hey can we put Google maps in here? Has this changed recently? Last I checked you would just drop a script tag into the page, who needs a library for that? Edit - I checked (https://developers.google.com/maps/documentation/embed/guide https://developers.google.com/maps/documentation/embed/guide), how does a framework make a copy/paste job any simpler? > "we need to integrate with stripe payments" I'm not familiar with stripe, but don't you just give it a return url? I don't see how a framework would help at all here. > you'll need to stay 100% up to date on all security issues/approaches/classes of vulnerability to make sure your custom system is secure. This is harder with a framework, it's one more thing to keep updated. The less libraries the less vulnerabilities.