News for hackers. Stuff that matters.

A comment on JavaScript-heavy approaches are not compatible with long-term performance goals. Parent comment

Re:JavaScript-heavy approaches are not compatible with long-... by pjmlp on Monday February 16, 2026 @03:31AM (#47032429)
It is very hard to avoid when you have Vercel doing partnerships with SaaS cloud providers that end up supporting only React and Next.js on their SDKs.

Even if other programming stacks are supported, they tend to be 2nd or 3rd class versus anything React.

Look into the ecosystem of headless products that have jumped into the whole MACH architecture hype cycle.

Then you have to justify to upper management, and partner support when problems arise why you are not using their SDK.

[ Parent | on HN ]
Re:JavaScript-heavy approaches are not compatible with long-... by mvdtnz on Monday February 16, 2026 @06:35AM (#47033821)
Why on earth would your cloud provider dictate your front end stack? My mind is in tatters trying to understand this thought process.
[ Parent | on HN ]
Re:JavaScript-heavy approaches are not compatible with long-... by pjmlp on Monday February 16, 2026 @06:57AM (#47033959)
Because they have these things called SDKs to extend their product, for specific programing languages.

Here is an example, https://www.sanity.io/studio

Want to extend the SaaS product for your backoffice users?

Learn React or make Studio from scratch.

Frontend stacks are also backend stacks in cloud products.

[ Parent | on HN ]
Re:JavaScript-heavy approaches are not compatible with long-... by mvdtnz on Monday February 16, 2026 @07:00AM (#47033973)
This looks like a SaaS vendor not a cloud provider?
[ Parent | on HN ]
Re:JavaScript-heavy approaches are not compatible with long-... by pjmlp on Monday February 16, 2026 @07:01AM (#47033986)
I wrote "SaaS cloud providers", I am yet to see a Saas solution on-prem.
[ Parent | on HN ]
Re:JavaScript-heavy approaches are not compatible with long-... by muvlon on Monday February 16, 2026 @06:44AM (#47033878)
Because with Next.js, Vercel was able to turn the frontend stack into also a really shitty backend stack. And it's particularly shitty at being deployed, so they're in the business of doing that for you.
[ Parent | on HN ]