3 ms·
Ehh I’m not sure if this is necessarily true. You can, in fact, completely separate front end from back end... but that distinction is very Blurred nowadays due
by torgian 6y ago
Ehh I’m not sure if this is necessarily true. You can, in fact, completely separate front end from back end... but that distinction is very Blurred nowadays due to front end frameworks requiring hundreds of Megs of code just to work.
It’s still possible to keep things simple, serve data from the server to the front end, and keep the front end purely visual.
Unfortunately this isn’t the case anymore; I think the current trend is making things harder to maintain overall and lowers the user experience.
- toomanybeersies 6y agoI feel like the distinction is more clear these days in the age of single page apps, not less. You can write clearly defined APIs for the transfer of data between the client and the server, and leave the implementation details to each team. It's possible to create an entire web app without anyone on the backend team communicating with anyone on the frontend team (although in my experience, this is a really bad idea).
- filleduchaos 6y agoWhat does that have to do with the article, though?