| ▲ | graemep 3 days ago | |||||||||||||||||||||||||
Yes, that is what I was asking about. I entirely agree. It is what I do when I have to - although I mostly do simple JS as I am a backend developer really, and if I do any front end its "HTML plus a bit of JS" and I just write JS loading stuff into divs by ID. When i have worked with front end developers doing stuff in react it has been a horrible experience. In the very worst case they used next.js to write a second backend that sat between my existing Django backend (which had been done earlier) and the front end. Great for latency! It was an extreme example but it really soured my attitude to complex front ends. The project died. | ||||||||||||||||||||||||||
| ▲ | athanagor2 3 days ago | parent | next [-] | |||||||||||||||||||||||||
> In the very worst case they used next.js to write a second backend that sat between my existing Django backend (which had been done earlier) and the front end. That's hilarious. Casey Muratori truly is right when he says to "non-pessimize" software (= make it do what it should do and not more), before optimizing it. | ||||||||||||||||||||||||||
| ▲ | usrbinenv 3 days ago | parent | prev [-] | |||||||||||||||||||||||||
Oh no, they do that? I thought Next.js is a fully functional backend itself, like Django. But I'm shocked to learn that it's just a middleman-backend to render templates that are already served from another backend. | ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||