Re:How we rebuilt Next.js with AI in one week
by judahmeek on Wednesday February 25, 2026 @01:08AM
(#47147934)
> Then once things are fairly stable and well-understood, another person can just yoink it.
That transparency & availability for community contributions or forks is the point of open-source.
If you're only using open-source as marketing because you're bad at marketing, then you should probably go closed source & find a non-technical business partner.
Whoever "yoinks" the package runs into the same problem because they now have to build credibility somehow to actually profit from it.
Re:How we rebuilt Next.js with AI in one week
by atrocious on Wednesday February 25, 2026 @04:43AM
(#47149443)
Established corporations will be doing yoinking, with a pre-existing credibility. There's a huge incentive to offer these copied services for cents on the dollar, as a way to kill the competition.
Re:How we rebuilt Next.js with AI in one week
by judahmeek on Wednesday February 25, 2026 @10:54AM
(#47153215)
Credibility doesn't transfer easily.
Anyone who yoinks an open-source package still has to present an argument about why their offering is better than the original maintainer's.
Re:How we rebuilt Next.js with AI in one week
by anematode on Wednesday February 25, 2026 @01:58PM
(#47156095)
When push comes to shove, cheapness and hype can shove.
Re:How we rebuilt Next.js with AI in one week
by atrocious on Friday February 27, 2026 @08:41AM
(#47180390)
I agree, but it's historically been as simple as "you already use AWS for everything else". For example, ElasticSearch.
Re:How we rebuilt Next.js with AI in one week
by remus on Thursday February 26, 2026 @07:56AM
(#47165431)
It'll be interesting to see if this happens at a service level too. Like how lots of companies offer an S3 compatible API, will companies start offering similar services and building a compatibility layer over the top as an easy way to for customers to transition? You could use the existing service as a test suite to check your compatibility API behaves the same as the original product.
Well said; this is my thinking as well. One person or organization can do the hard work of testing multiple approaches to the API, establishing and revising best practices, and developing an ecosystem. Then once things are fairly stable and well-understood, another person can just yoink it.
I have little empathy for Vercel, and here they're kind of being hoist by their own petard of inducing frustration in people who don't use their hosting; but I'm concerned about how smaller-scale projects (including copyleft ones) will be laundered and extinguished.