4 ms·
Why Gatsby, specifically? This seems like an odd choice.
by bovermyer 4y ago
Why Gatsby, specifically?
This seems like an odd choice.
- onion2k 4y agoI think it's an acquihire. They don't necessarily want Gatsby. They want the team who built Gatsby.
- ferdowsi 4y agoStrange time to do an acquihire given that Netlify just had a round of layoffs.
- bdcravens 4y agoJust means Gatsby's talent is more desired than those they employed.
- reducesuffering 4y agoI'm surprised this was the only other comment so far about it. It has to be an acquihire. Gatsby is a dead framework going forward.
- goodoldneon 4y agoWhy is it dead?
- reducesuffering 4y agoCheck the 5 year chart trajectory: https://npmtrends.com/gatsby-vs-next https://npmtrends.com/gatsby-vs-next and https://insights.stackoverflow.com/trends?tags=gatsby%2Cnext.js https://insights.stackoverflow.com/trends?tags=gatsby%2Cnext...
- LunaSea 4y agoWhat are the alternatives?
- reducesuffering 4y agoNext.js the comparison shown in those charts
- LunaSea 4y agoI would not consider Next.js an alternative as it's missing a lot of the static website generation features. I don't think that it has server side GraphQL and Typescript support with data preloading from headless CMSs.
- crummy 4y agoAstro.build perhaps
- nsonha 4y agotry it and you'll see, also have you heard the name Gatsby in the past 2 years? I think not.
- Alifatisk 4y agoWhy do you call it a dead framework?
- winrid 4y agoGatsby Cloud, maybe?
- dudeinjapan 4y agoReserving judgements is a matter of infinite hope.