News for hackers. Stuff that matters.

A comment on We moved Railway's frontend off Next.js. Builds went from 10+ mins to under two. Parent comment

Re:We moved Railway's frontend off Next.js. Builds went from... by itopaloglu83 on Wednesday April 08, 2026 @05:02AM (#47687367)
It’s mind blowing when you check the generated code, because it goes over 50 elements deep for a simple looking website.

Makes me think that there’s no way this is computationally efficient either.

[ Parent | on HN ]
Re:We moved Railway's frontend off Next.js. Builds went from... by crooked-v on Wednesday April 08, 2026 @05:09AM (#47687425)
That particular issue is nothing to do with Next or React and everything to do with how HTML/CSS is a really shitty layout engine.
[ Parent | on HN ]
Re:We moved Railway's frontend off Next.js. Builds went from... by maccard on Wednesday April 08, 2026 @05:35AM (#47687679)
Hard disagree. This is JavaScript frameworks building a hierarchy for themselves and ignoring any sort of complexity on the generated DOM. There’s 0 reason for these 8-10 nested divs other than that’s what the framework spits out.
[ Parent | on HN ]