Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

We moved Railway's frontend off Next.js. Builds went from 10+ mins to under 2

blog.railway.com

Post reply on HN
Print view View original

141–150 of 230 posts

Re: We moved Railway's frontend off Next.js. Builds went from 10+ mins to under 2

#141

Post by chrisweekly »

SilverSlash wrote: post #35
tgdn wrote: post #7

We went through a very similar migration. Had a Next.js landing page and a separate TanStack Router SPA - consolidated both into a single Vite + TanStack Start app. Same experience with build times and the architecture mismatch: our app is heavily client-side with real-time state, and fighting Next.js's server-first assumptions wasn't worth it. TanStack Router's type-safe routing and file-based route generation have…

I hadn't heard of TanStack but a quick look at their website doesn't inspire confidence tbh. I mean, just take "TanStack Pacer". It provides such things as: ``` import { Debouncer } from '@tanstack/pacer' // class const debouncer = new Debouncer(fn, options) debouncer.maybeExecute(args) // execute the debounced function debouncer.cancel() // cancel the debounced function debouncer.flush() // flush the debounced funct…

Not to feed the trolls, but you responded to a comment about TanStack Start (a full-stack metaframework) by denigrating @tanstack/pacer -- a separate, niche utility published by the same team.

You're entitled to your opinions, but I'm happy to defend the rationale of leveraging battle-hardened, rigorously-tested, open-source, type-safe libraries instead of DIY cowboy vanilla js spaghetti.

Re: We moved Railway's frontend off Next.js. Builds went from 10+ mins to under 2

#142

Post by tacker2000 »

chrisweekly wrote: post #138
tacker2000 wrote: post #108

Earlier quoted context omitted.

TanStack started out by providing a very good JS table library. Now they offer a Router, and some more libs. They are definitely an up and coming name in the JS space.

That's... not quite right. [EDIT] I typed "Router" when I meant "Query". TanStack Query is the relatively newer name for React Query -- one of the most popular JS libraries of all time. TanStack Start is a recent metaframework (and the one w/ the brightest future, IMO), but Tanner and team have profoundly significant bona fides. IOW, the dev team is far from being the "new kids on the block".

That's... not quite right :)

React Router, which belongs to Remix, which was acquired by Shopify, is here: https://github.com/remix-run/react-router

Tanstack Router is an entirely new router.

Re: We moved Railway's frontend off Next.js. Builds went from 10+ mins to under 2

#143

Post by wouldbecouldbe »

kennu wrote: post #89
xandrius wrote: post #75

Earlier quoted context omitted.

Why is everyone so afraid to get a $5/mo Ubuntu/Debian VPS, install nginx and call it a day? Then you can even run multiple projects off the same server.

It means you take responsibility of maintaining the server forever, i.e. dealing with TLS certificates, SSH keys, security updates, OS/package updates, monitoring, reboots when stuck, redeploy when VPS retired, etc. Usually things work fine for a year or two and then stuff starts to get old and need attention and eat your time.

just ask claude to do all that :), he is excellent and installing & managing new servers and making sure all security patches are updated. Just be careful if its a high risk project.

Re: We moved Railway's frontend off Next.js. Builds went from 10+ mins to under 2

#144

Post by wouldbecouldbe »

kennu wrote: post #114
shimman wrote: post #94

Earlier quoted context omitted.

This is extremely easy with tools like dokploy tho... I use dokploy locally to manage all my VPSs + home server. Truly good stuff and I don't believe your quip at the end, it feels like poisoning the open source waters for consolidated anti democratic cloud platforms. It's way way way way easier managing a basic VPS that can be highly performant for your needs. If this was 2010, I'd agree with you but tooling and pra…

Maybe you're right - I've never tried dokploy, but from documentation it sounds like mostly a deployment, monitoring and alerting tool. For me the problem has always been that once you get the alert (or something just stops working), a human needs to react to it and make things work again. In cloud services you mostly pay for them providing the human, and in self-hosting you're the human. I can see though that today'…

yeah i've had more downtime on managed db's & cloud servers then on my own managed VPS. And if it happens, with VPS i can normally fix it instantly compared to waiting 20-60 min for a response, just to let you know they start fixing it. And when they fix it, it doesnt always mean your instance automatically works.

Re: We moved Railway's frontend off Next.js. Builds went from 10+ mins to under 2

#145

Post by chrisweekly »

SahAssar wrote: post #140
chrisweekly wrote: post #138

Earlier quoted context omitted.

That's... not quite right. [EDIT] I typed "Router" when I meant "Query". TanStack Query is the relatively newer name for React Query -- one of the most popular JS libraries of all time. TanStack Start is a recent metaframework (and the one w/ the brightest future, IMO), but Tanner and team have profoundly significant bona fides. IOW, the dev team is far from being the "new kids on the block".

Do you have a source for TanStack Router being a newer name for React Router? Doesn't seem like it when looking at the sites for both projects. Are you thinking of the whole Remix/ReactRouter thing?

(facepalm)

Thank you, but no. I typed "Router" when I meant "Query". TanStack Query is the newer name for the library FKA react-query.

TanStack Router is an alternative to React Router.

TanStack Start is an alternative to Remix/react-router-7's framework mode.

The naming history and evolution of react-router and its relationship to Remix is a bit convoluted, but an unrelated tangent to the point I was making.

Re: We moved Railway's frontend off Next.js. Builds went from 10+ mins to under 2

#146

Post by mschuster91 »

sosodev wrote: post #87
cryptonym wrote: post #24

Earlier quoted context omitted.

Is server-rendered HTML that bad for 2026 web or is everyone building complex apps? Many of my customers insists on using Next.js or similar but when I browse their website I don't get the point. They are downloading and executing megabytes of JS while in-page interactions tends to be limited to few basic stuff. Never seen one of their project requiring offline mode. Maybe that's being able to easily replace a [FRAME…

I think the unfortunate truth is the simplest. Web development has long been detached from rationality. People are drawn to complexity like moths to a flame.

> People are drawn to complexity like moths to a flame.

Not to complexity, but to abstraction. The more something is abstracted away, the more fungible "developers" become, to the eventual tune of Claude Code.

No one cares that trying to debug a modern application is as hellish as its performance, the KPI that executives go for is employment budget.

Re: We moved Railway's frontend off Next.js. Builds went from 10+ mins to under 2

#147

Post by chrisweekly »

tacker2000 wrote: post #142
chrisweekly wrote: post #138

Earlier quoted context omitted.

That's... not quite right. [EDIT] I typed "Router" when I meant "Query". TanStack Query is the relatively newer name for React Query -- one of the most popular JS libraries of all time. TanStack Start is a recent metaframework (and the one w/ the brightest future, IMO), but Tanner and team have profoundly significant bona fides. IOW, the dev team is far from being the "new kids on the block".

That's... not quite right :) React Router, which belongs to Remix, which was acquired by Shopify, is here: https://github.com/remix-run/react-router Tanstack Router is an entirely new router.

Thanks yes I know, I typed "Router" meaning "Query", noted in a peer comment. sigh.

Re: We moved Railway's frontend off Next.js. Builds went from 10+ mins to under 2

#148

Post by nchmy »

fnoef wrote: post #130
kennu wrote: post #89

Earlier quoted context omitted.

It means you take responsibility of maintaining the server forever, i.e. dealing with TLS certificates, SSH keys, security updates, OS/package updates, monitoring, reboots when stuck, redeploy when VPS retired, etc. Usually things work fine for a year or two and then stuff starts to get old and need attention and eat your time.

Oh no! Issuing SSL certificates! The horror! I really doubt that people who can’t install an ssh key should be able to practice software engineering. Sometimes, I think that software engineering should be a protected profession like other types of engineering. At least it will filter out the people who can’t keep their OS up to date.

Caddy server even does ssl for you automatically.
Post reply on HN