How we rebuilt Next.js with AI in one week

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.

[ Parent | on HN ]

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.

[ Parent | on HN ]

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.

[ Parent | on HN ]

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.

[ Parent | on HN ]

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.

[ Parent | on HN ]