4 ms·
> That's just your choice of how to build your app, right? You could've avoided this by rendering templates on the server and sending static HTML to the client,
by rambambram 4y ago
> That's just your choice of how to build your app, right? You could've avoided this by rendering templates on the server and sending static HTML to the client, keeping the business logic on the server.
Exactly. This way of working is such a breeze. PHP does the logic, the state is firmly in the database, and I'm from a time when peopling talking "frontend" meant HTML and CSS. Occasionally some plain JS, and I'm good.
Years ago I was out of the webdev field for some time, and I must admit that HTML and CSS alone have made big strides.
- gbalduzzi 4y ago> and I'm from a time when peopling talking "frontend" meant HTML and CSS When that is the case, the stack you are describing is just perfect even nowadays. The problem is, in most cases that is just not the case anymore.
- rambambram 4y agoI guess that's it. It's the difference between the "application" and "document system" that some other commenter talked about. I guess the wisdom comes down to knowing which one to choose in what situation. I myself am looking to find the edges of building a web application with the "document system". Clicks and requests for a full page load don't matter that much if you're able to keep your app simple. Which is also defined by context, not only by programming skills. Certain situations or applications are just not suited for the "document system".