4 ms·
I don't understand your argument at all. Why would a TS backend be inferior to a PHP backend, for example? Because for many people, that's the tradeoff. Think
by moritzwarhier 3y ago
I don't understand your argument at all. Why would a TS backend be inferior to a PHP backend, for example?
Because for many people, that's the tradeoff.
Think of a new project.
You'll still have "OOP" PHP + some random templating language + the infamously hard to do "sprinkles" of JS.
In the end lots of people start to shoehorn their PHP or Django CMS into REST API parts anyway, reinventing the wheel over and over again, for every new requirement.
I have nothing against PHP or Django or other server technologies with corresponding templating languages.
But to churn on the "old and proven" point in 2023 seems odd to me.
It's tradeoffs all the way down.
- boringuser2 3y agoA TS backend is inferior to a PHP backend merely due to available frameworks being night and day in favor of PHP.
- paulddraper 3y agoA TS backend is going to have a SPA frontend, reducing the complexity of the backend significantly. Use Koa and a database client and you're good.
- boringuser2 3y agoPHP isn't "complex", it's nearly identical with minor variations.
- paulddraper 3y agoMy point is that the need for a backend "framework" decreases significantly if you take that burden on the frontend. And anyone writing a JS/TS backend is likely doing that. So I would expect fewer "frameworks."
- boringuser2 3y agoWhat kind of operations do you imagine an application is used for?