3 ms·
> I think this is largely because people are writing JS on the frontend, and it's easier to do SSR with the code you've already got That and those writing JS o
by TacticalCoder 4y ago
> I think this is largely because people are writing JS on the frontend, and it's easier to do SSR with the code you've already got
That and those writing JS on the frontend are, among all the devs out there, those the more likely to be working on SSR pages.
- ratww 4y agoCorrect. Most backend engineers today do only the APIs to be consumed by the frontend. And there always was some sort of a separation in the industry: I remember when in some enterprisey places there was the strange role of "webdesigner" or some other (often incorrect) term that was half-designer half-programmer that only took care of HTML/CSS. Javascript was used very sparsely. There were several frameworks whose whole spiel was to allow people not to write HTML/CSS/JS. Anyone doing both the backend and the HTML/CSS part was considered a bit of a unicorn, even back then. For a lot of self-taught people doing "everything" was the norm, but in the industry it wasn't. Then came Bootstrap etc and sorta equalised everything. Then came Angular and React and we needed a name for people doing the HTML/CSS/JS work. When rendering on the server became a focus again, the responsibility of writing the markup once again fell on people able to do HTML/CSS. Which means frontend developers. Which means JS.