3 ms·
> What vendor lock-in? Most of the code is just vanilla JS. That runs in a specific environment with vendor-specific IAM configurations, vendor-specific DNS co
by troupo 2y ago
> What vendor lock-in? Most of the code is just vanilla JS.
That runs in a specific environment with vendor-specific IAM configurations, vendor-specific DNS configurations, vendor-specific network configurations, vendor-specific service integrations, vendor-specific runtimes and restrictions, vendor-specific...
- solardev 2y agoThat sounds like an AWS thing? There's a lot of frameworks that can deploy straight to Vercel, Cloudflare Pages, Netlify, etc. without all that. And if you really want to manage all that, it would apply to both PHP sites and JS and anything else. That's really more of a discussion of fully vs partially managed cloud solutions, not PHP or JS or any framework in particular.
- troupo 2y ago> There's a lot of frameworks that can deploy straight to Vercel, Cloudflare Pages, Netlify, etc. without all that. All of them need all that. And those frameworks are for a reason: they sweep a lot of these things under a rug, and after a certain complexity you will have a vendor lock-in. Just because you will end up depending on certain policies that other vendors don't provide. Or on certain services that other vendors don't provide. Or guarantees that other vendors don't provide. Or pricing that... Or...
- solardev 2y agoCan you provide some examples? This hasn't been my experience, as a web dev who switched from PHP to such frameworks. There's so much less complexity and maintenance overall, IMHO, but maybe we're looking at different facets of it?