Given this is achieved with CSS, there is no reason that users can't disable animations with a user style sheet. In fact this is what some users do, according to a CSS Working Group discussion about disabling view transitions.

Some users do set transition-duration: 0 !important in user style sheets in order to prevent transitions, same with animation: none !important or so.

Could you give more context about what Vercel features you need - is the site statically generated, or do you also need Vercel Functions?

Great question. Are you framing this in terms of employment opportunities, the end user experience, or both?

Agreed though the article has this disclaimer:

Before we dive into the code, I think it’s worth pointing out that the goal is largely to be immersive and expose some lore. I think this design and effect fit because of the theme and because it’s not for critical content. My point is that it’s just an aesthetic component for a game that makes this acceptable — I don’t think this is necessarily a good user experience for your every day website where there are stakes.

There are several European based alternatives to Vercel. It's also worth having a read through or posting to !web_hosting@programming.dev

Though that quote is followed by this, which indicates at least five of those vulnerabilities were real:

I searched the Linux kernel and found a total of five Linux vulnerabilities so far that Nicholas either fixed directly or reported to the Linux kernel maintainers, some as recently as last week:

Your comment reminded me of this article, The Software Quality and Productivity Crisis Executives Won’t Address, which discusses the lack of technical leadership when it comes to tackling technical debt, and that the solution is usually a rewrite.

Instead, most organisations don’t tackle technical debt until it causes an operational meltdown. At that point, they end up allocating 30–40% of their budget to massive emergency transformation programmes—double the recommended preventive investment (Oliver Wyman, 2024).

I have noticed the repository lacks CONTRIBUTING.md. If you want to set some rules about contributing, I would have added them there, instead of creating a Markdown file specific for agents. I'm very much of the philosophy that you should write documentation for humans, which has the added bonus that it will also be consumed by agents.

It's definitely got the worst defaults compared to the alternatives.

pnpm, Bun, and Deno have all made better choices about their defaults. pnpm blocks postinstall scripts, Bun requires explicit opt-in for them, Deno’s permission model is restrictive by design.

I agree but it depends on how teams create and refine their tickets. For example, you could have high level tickets, and someone picks one up and creates an implementation that's not an appropriate fit for your architecture.

Thank you for not assuming my motivations. Could you please elaborate on what you mean by "oneshotted"? I share a lot of articles, so I'm not surprised you recognise my username.

I don't specifically seek them out. I follow quite a few different programming blogs, and I am just sharing what people are posting about, and it just so happens a lot of people are posting about this topic.