|
|
|
|
|
by thinkingkong
966 days ago
|
|
Moving past the excellent joke. The problem I see with Next has nothing to do with re-visiting these concepts, and almost everything to do with the examples. Flipping your mindset from “react is a framework for client side rendering” to “react is a dsl for building HTMl on the server” is a leap and it brings all this junk with it. I think thats how we get these parodies, and the “sql in a component” nonsense. What is missing though is guidance on how to clearly separate these things. How do you do permissions, security model, clear separation of concerns, etc within nextjs in this new world? This is not new ground so the patterns should be pretty easy to describe. But thats missing and as a result, we do have people saying “no no. The process.exec call was a demo” without realizing that people are going to refer to that as a best practice. |
|
Whats quite amusing to me in the context of this joke, is back in the late 2010s we actually used React this way in PHP via the V8JS PHP extension lol
In production, too.