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

131–140 of 230 posts

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

#131

Post by kennu »

SoftTalker wrote: post #125
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.

vs. trusting someone else to do all that for you, and do you then verify that it gets done properly?

When buying the infrastructure as a managed cloud service, yes, I trust that they've got people handling it better than I could myself. The value proposition is that I don't even see the underlying infrastructure below a certain level, and they take care of it.

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

#132

Post by asadm »

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.

Time is a precious (and really expensive for SWEs) resource, why should one spend it on updating certs and instances?

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

#133

Post by chrisweekly »

ricardobeat wrote: post #99
mattmanser wrote: post #97

Earlier quoted context omitted.

Who remembers sprite sheets? Does that give my age away? I did an optimization pass for a client once where I got rid of a ton of the sprites but didn't have the energy to redo it all, so it just had huge sections that were blank. Super snappy loading afterwards though.

Yes, good times! With http2/3 they don't really matter anymore though, you get similar benefits from request pipelining.

Spriting is actually harmful for performance except in specific HTTP-1 scenarios.

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

#134

Post by bastardoperator »

petcat wrote: post #78
miyuru wrote: post #36

I just tried their domains page it took 10.8MB of data and took 2s for the DOM to be ready. page actually took 17s to fully render with multiple shift changes. all to render a domain search bar similar to google home page. https://railway.com/domains

web dev is a sewer All my projects are server rendered with jinja/minijinja, bootstrap, jQuery, and htmx when I need a little bit of SPA behavior on forms. No builds, just static <script src= tags. Very fast and easy. I'll never recommend anything else.

Sounds more difficult then modern web frameworks. We've all done this for little projects, but anything with users or development teams, your method is DOA.

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

#135

Post by ipsento606 »

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.

certbot and ssh keys are things you set up once

I haven't rebooted my DO droplets in something like 5 years. I don't monitor anything. None of them have been "retired".

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

#136

Post by kennu »

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.

This is not about how easy or difficult it is to issue TLS certificates, to configure SSH keys or to update the OS. It's about having to actively maintain them yourself in every possible situation until eternity, like when TLS versions are deprecated, SSH key algorithms are quantum-hacked, backward-incompatible new OS LTS versions are released, and so on. You will always have new stuff come up that you need to take care of.

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

#137

Post by OJFord »

anematode wrote: post #110
hazelnut wrote: post #81

Earlier quoted context omitted.

same here and I'm using a beefy MacBook (Apple M4 Max, 64gb ram). something is wrong with the front end code. there are a lot of animations, so my hunch would be that something goes wrong there.

Moore said computers get twice as fast every 18 months. Web devs took that as a challenge.

He said transistor count on chip doubles. (The more accurate pithy comment would be they took it as available resources.)

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

#138

Post by chrisweekly »

tacker2000 wrote: post #108
SilverSlash wrote: post #35

Earlier quoted context omitted.

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…

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".

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

#139

Post by anematode »

OJFord wrote: post #137
anematode wrote: post #110

Earlier quoted context omitted.

Moore said computers get twice as fast every 18 months. Web devs took that as a challenge.

He said transistor count on chip doubles. (The more accurate pithy comment would be they took it as available resources.)

U+1F913

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

#140

Post by SahAssar »

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".

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?

Post reply on HN