ORM: don't need, I can write SQL. Prepared statements sufficient to prevent SQL injection. Both PHP and Go have good database abstraction libraries.
Sockets: Don't use but if I did I wouldn't need a framework.
SPA: I don't write apps that way. Server-side, which is why we're talking specifically about PHP and Go.
Queue handler, scheduler: Can easily do in the database or with Redis.
Container: What? Do you mean something like Docker? That has nothing to do with the web app development language or framework.
Auth: OAuth2 and SAML not a big deal, but maybe worth introducing a dependency depending on requirements. Regular username/password/MFA auth easy to implement, certainly no framework needed for that.
Likewise with routing, "MVC" structure, etc. Frameworks can save some time beginning but eventually you have to debug them, or run into limitations to work around. And one day the framework gets updated and you have to deal with breaking changes.
I highly doubt the technical debt and inevitable vulnerabilities weigh up any perceived time saved.
Also when you use a framework like laravel you're sort of forced into building applications in similar styles making it easier for other developers to cooperate instead of having to figure out some weird homemade framework.
If you're making a wheel that exactly fits the design requirements you'll have a hard time when does requirements inevitably changes. Making rigid designs instead of plyable is a terrible idea if you're working with web
None of those sound like frameworks, just plain libraries that, if integrated properly, are easily swapped out if they become a liability later.
Both PHP and Go already provide the framework as part of the standard installation. Everything else you need should be pluggable libraries. If developers are pulling shenanigans with those libraries to try and make them frameworks, beware.
gregjor|1 year ago
Sockets: Don't use but if I did I wouldn't need a framework.
SPA: I don't write apps that way. Server-side, which is why we're talking specifically about PHP and Go.
Queue handler, scheduler: Can easily do in the database or with Redis.
Container: What? Do you mean something like Docker? That has nothing to do with the web app development language or framework.
Auth: OAuth2 and SAML not a big deal, but maybe worth introducing a dependency depending on requirements. Regular username/password/MFA auth easy to implement, certainly no framework needed for that.
Likewise with routing, "MVC" structure, etc. Frameworks can save some time beginning but eventually you have to debug them, or run into limitations to work around. And one day the framework gets updated and you have to deal with breaking changes.
Mrdarknezz|1 year ago
mplewis|1 year ago
the_real_cher|1 year ago
cjs_ac|1 year ago
A framework with all the bells and whistles isn't that great when I want a framework with a piano.
Mrdarknezz|1 year ago
randomdata|1 year ago
Both PHP and Go already provide the framework as part of the standard installation. Everything else you need should be pluggable libraries. If developers are pulling shenanigans with those libraries to try and make them frameworks, beware.