You don't need Next.js – Why we migrated from Next to React

Re:You don't need Next.js – Why we migrated from Next to React by mzronek on Wednesday January 01, 2025 @02:20PM (#42568472)

Using server-side templating is another layer of complexity on top of your stack, that just glues together your output. These template languages are not easy to learn. Custom code for loops, escaping, template inheritance etc. Sometimes these are also hard to debug. The documentation of Jinja is huge.

Things get worse when you bring Javascript into the mix. You need to create Javascript code with your template engine without any Javascript toolchain.

Hard no to the string concat approach for me.

[ Parent | on HN ]

Re:You don't need Next.js – Why we migrated from Next to React by TekMol on Wednesday January 01, 2025 @02:38PM (#42568620)

How is React easier to learn and debug?

[ Parent | on HN ]

Re:You don't need Next.js – Why we migrated from Next to React by mzronek on Wednesday January 01, 2025 @03:22PM (#42568964)

With Full-Stack React you will use JSX to directly render HTML. Logic is done with Javascript, so you don't need to learn an additional language. There is also no mapping to Javascript and you can use the standard toolchain (for debugging).

[ Parent | on HN ]

Re:You don't need Next.js – Why we migrated from Next to React by TekMol on Thursday January 02, 2025 @03:30AM (#42572742)

How does JSX "directly" render to HTML? Have you compared the codebase of the React to EJS? EJS is much more direct. And the logic is also Javascript.

What do you mean by "no mapping to Javascript"? It is not as if React is part of the Browser API.

[ Parent | on HN ]

Re:You don't need Next.js – Why we migrated from Next to React by mzronek on Thursday January 02, 2025 @03:34AM (#42572757)

How do you get the server-side data to client-side Javascript? For example an array of strings or an object.

[ Parent | on HN ]