Why would ANYONE buy Gatsby??

preview_player
Показать описание
I did not expect Netlify to buy Gatsby but...here we are. My take on this might surprise you.

#gatsby #netlify

Рекомендации по теме
Комментарии
Автор

Wait....is Theo growing a PrimeStache?

RobertFerentz
Автор

here before the "stupid netlify, you can use gatsby for free" jokes

samuelgunter
Автор

The crazy-eye stare wasn't enough, the stache really drove it home. Nicely done. Waiting for the Netflix special on the bodies you keep in your basement.

creatorsremose
Автор

Gatsby was fine; it was pioneering in many ways. The later frameworks (including Next with its SSG, ISR, etc.) have the huge advantage that they can learn from Gatsby's mistakes and choose a better way.

hynekss
Автор

Back then I built an image heavy website and Gatsby was by far the better option. It is similar to today's Next's Image optimization but Gatsby had that years ago and it was the best(IMO it is still better because you could easily do image blurring and other effects while the full image is loading and it was extremely fast). Also, all the plugins made it so easy to connect to any CMS, - with mostly everything provided out of the box. It truly was like the Wordpress for React devs. I think Gatsby pioneered many features that we see today in other frameworks.

ari.joel.m
Автор

I’m probably the outlier here in that I used Gatsby to learn React. It was a combination of where I was at in looking at alternatives to React, along with the practicality of being able to deploy a static website. The side project that I used Gatsby for ended up being some thing I left to the wayside. I think there are a dozen or so dependencies that I’m getting warnings for now, and I just kind of gave up on maintaining it.

glamshell
Автор

You make an excellent point, I was wondering about why Netlify would do this, with so many other superior, more modern static site generators. But there isn´t a dearth of SSG, there is a dearth of flexible marshalling of content ... with ContentLayer in Next, with Nuxt´s Content module, and with Astro 2´s content collections, etc., all attempting to address this fundamental gap... and yes, Gatsby got this right, right from the start. Even the guy who wrote what is today WPGraphQL now works for WP Engine and no longer for Gatsby. So, yes, Netlify´s move is brilliant. Thanks for pointing that out so succinctly!

demystifyingdev
Автор

If you have an old Wordpress site, and want to move to something more modern like this, is the idea to keep using Wordpress for content management? Keep creating content in Wordpress, but use it as a headless CMS? And then use the datalayer to fetch content from Wordpress, and bang it out in a modern framework?

whitefluffycloud
Автор

I am still missing a library that you can plug into your express project that transforms a specific route path and just that route into a static website with island type hydration. Researching I ended up using bare React dom server giving up partial hydration as other frameworks don’t seem to be “humble” enough to fit into other projects and instead demand to be the main focus of the project. Perhaps my use case is very niche.

pif
Автор

I have to say - coming from CRA, I genuinely loved working with gatsby. Things like routing and programmatic page generation in node were so easy and intuitive, the cool things you could do in the browser file, the satisfaction of ssg instant page loading coming from CRA, the link and image components… I don’t agree with some of these other comments that the dx was shit. I probably wouldn’t use it for a new site, but still maintain some stuff in it today and have a good time.

michaelblum
Автор

Stupid Netlify, you can use Gatsby for free

EddyVinck
Автор

Mom: Stached Theo cannot hurt you kiddo.
Stached Theo:

cowabunga
Автор

I started React with Gatsby and I hated and didn't touch it for 2 years after that. (I was PHP dev back then)

kubre
Автор

Try using ultraviolet shampoo and conditioner - helps with yellowing

mako
Автор

I run Gatsby for a big company for 2 years! we HAD to move to nextjs because of Gatbyjs Memory issue on bigger sites!!! and thats why they build the Cloud version of it!

ehsanpo
Автор

It was interesting when I moved out of Wordpress, but now that Astro is out, Gatsby looks super bloated and over engineered to generate static websites.

pedroserapio
Автор

Wtf I voted Keep on twitter poll, Now I see the video get rid off the stash

kubre
Автор

That point of modern WordPress integration can be a key.

hamzahmd_
Автор

Agree. With Next.js or Astro, Gatsby is slowly becoming non appealing for SSG. I think the data layer argument is valid and can be a good way to at least use headless WordPress as a CMS. The only issue is that even as headless, WordPress will make you use plug-ins that may or may not be maintained.

toddribnek
Автор

Mate is your white balance different to your other videos ? Or maybe im just tripping

devinda_me