Why would ANYONE buy Gatsby??

แชร์
ฝัง
  • เผยแพร่เมื่อ 7 ก.พ. 2025
  • I did not expect Netlify to buy Gatsby but...here we are. My take on this might surprise you.
    #gatsby #netlify
    ALL MY VIDEOS ARE POSTED EARLY ON PATREON / t3dotgg
    Everything else (Twitch, Twitter, Discord & my blog): t3.gg/links

ความคิดเห็น • 96

  • @RobertFerentz
    @RobertFerentz 2 ปีที่แล้ว +300

    Wait....is Theo growing a PrimeStache?

    • @Hobbitstomper
      @Hobbitstomper 2 ปีที่แล้ว +72

      He tried the PrimeHoody but didn't like it. He tried Rust, but didn't like it. So now it's time to try out the PrimeStache.

    • @vedantnn7
      @vedantnn7 2 ปีที่แล้ว +42

      TheTheogen

    • @rbp365
      @rbp365 2 ปีที่แล้ว +4

      RustVimStache

    • @wilsonwg
      @wilsonwg 2 ปีที่แล้ว +4

      BlazingfastStache

    • @rumplstiltztinkerstein
      @rumplstiltztinkerstein 2 ปีที่แล้ว +5

      The name... is Theogen.

  • @samuelgunter
    @samuelgunter 2 ปีที่แล้ว +37

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

    • @demystifyingdev
      @demystifyingdev 2 ปีที่แล้ว +1

      but you can´t use Gatsby developers for free

    • @stoogel
      @stoogel 2 ปีที่แล้ว +1

      Soon Gatsby will "work best with Netlify"

  • @creatorsremose
    @creatorsremose 2 ปีที่แล้ว +7

    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.

  • @hynekss8618
    @hynekss8618 2 ปีที่แล้ว +29

    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.

    • @IgorTr
      @IgorTr 2 ปีที่แล้ว +1

      What were gatsby's mistakes?

    • @hynekss8618
      @hynekss8618 2 ปีที่แล้ว +1

      ​@@IgorTr I was having a lot of trouble with the "gatsby-node" api (which was important for routing and other stuff). In my opinion, it was confusing and not adequately documented. Also, lots of errors due to incompatible Gatsby / Node / plugins. The mandatory GraphQL was a debatable decision as well. Bottom line: not enough maturity and not the right abstractions. Then Next 10 came with a simpler api, both SSR and SSG (and ISR) and it was over.

  • @codelikeaninvestor
    @codelikeaninvestor 2 ปีที่แล้ว +2

    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.

  • @ari.joel.m
    @ari.joel.m 2 ปีที่แล้ว +3

    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.

  • @demystifyingdev
    @demystifyingdev 2 ปีที่แล้ว +1

    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!

  • @whitefluffycloud
    @whitefluffycloud 2 ปีที่แล้ว +5

    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?

    • @IgorTr
      @IgorTr 2 ปีที่แล้ว +1

      Yes

  • @michaelblum4557
    @michaelblum4557 2 ปีที่แล้ว

    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.

  • @pif5023
    @pif5023 2 ปีที่แล้ว +3

    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.

  • @mako3010
    @mako3010 2 ปีที่แล้ว

    Try using ultraviolet shampoo and conditioner - helps with yellowing

  • @EddyVinck
    @EddyVinck 2 ปีที่แล้ว +5

    Stupid Netlify, you can use Gatsby for free

  • @RedStone576
    @RedStone576 2 ปีที่แล้ว +3

    to try to compete against vercel

  • @cowabunga2597
    @cowabunga2597 2 ปีที่แล้ว +1

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

  • @ehsanpo
    @ehsanpo 2 ปีที่แล้ว +1

    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!

    • @Solarplexus0
      @Solarplexus0 ปีที่แล้ว

      This is an important aspect to consider. Thanks for sharing your experience

  • @kubre
    @kubre 2 ปีที่แล้ว +5

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

  • @dinckelman
    @dinckelman 2 ปีที่แล้ว

    Of all companies, this makes a ton of sense for netlify specifically

  • @pedroserapio8075
    @pedroserapio8075 2 ปีที่แล้ว +1

    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.

  • @devinda_me
    @devinda_me 2 ปีที่แล้ว +2

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

    • @t3dotgg
      @t3dotgg  2 ปีที่แล้ว +4

      Yeah playing with warmer lighting, I think I much prefer this

    • @devinda_me
      @devinda_me 2 ปีที่แล้ว +1

      @@t3dotgg Agreed, I find warmer tones great with human subjects, but your skin tone is a bit flushed here ( unless ofc you just made this after the bar, in which it makes sense 🤣)

  • @mosescosme8629
    @mosescosme8629 2 ปีที่แล้ว +1

    Not gonna lie, as a Gatsby fanboy, I was expecting you to just sh*t all over Gatsby and I was ready to defend it. But we agree completely on this point. That's neat lol

  • @toddribnek6660
    @toddribnek6660 2 ปีที่แล้ว

    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.

  • @lutfiikbalmajid
    @lutfiikbalmajid 2 ปีที่แล้ว

    few years ago using gatsby, and it not good dx for me. i dont know for now

  • @hamzahmd_
    @hamzahmd_ 2 ปีที่แล้ว

    That point of modern WordPress integration can be a key.

  • @WojciechKauznymr
    @WojciechKauznymr 2 ปีที่แล้ว

    DataLayer and Images -> these are gatsby strong suites. Nextjs desperately needs a datalayer...

  • @dixztube
    @dixztube 2 ปีที่แล้ว

    That stash is legit. Keep dat ! He’s morphin into prime 😂 hoodies next month while prime goes super saiyain 2 and wear fresh cuts.

  • @samuelgunter
    @samuelgunter 2 ปีที่แล้ว +6

    Netlify bought 2018

    • @t3dotgg
      @t3dotgg  2 ปีที่แล้ว +1

      I figured you out - you're only first because you steal content 👀

    • @peopledrivemecrazy
      @peopledrivemecrazy 2 ปีที่แล้ว +1

      Gatsby bought netlify (¬,‿,¬)

  • @kubre
    @kubre 2 ปีที่แล้ว +2

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

  • @jrupp2823
    @jrupp2823 2 ปีที่แล้ว

    ok can’t lie the mustache looks good

  • @Ironication
    @Ironication 2 ปีที่แล้ว

    Digging the new stache

  • @shounakb
    @shounakb 2 ปีที่แล้ว +2

    1:11 That "Somebody" is probably Fireship, isnt he?

    • @ghun131
      @ghun131 2 ปีที่แล้ว +1

      Man I wish someone would tag Fireship here

  • @wobsoriano
    @wobsoriano 6 หลายเดือนก่อน

    Theo uhm we need a new video 😅

  • @arturamorfati
    @arturamorfati 2 ปีที่แล้ว

    congrats 100k!

  • @ngprnk
    @ngprnk 2 ปีที่แล้ว

    They wanted to get developers behind it not the framework itself. ?

  • @sbstnssndn4868
    @sbstnssndn4868 2 ปีที่แล้ว

    I know it's none of my biz but I think you look better without it.

  • @Kerngebruiker
    @Kerngebruiker 2 ปีที่แล้ว

    Maybe they’ll just strip mine Gatsby to displace their user base only spiegelton knows

  • @Nonsense116
    @Nonsense116 2 ปีที่แล้ว

    Goodness that stache is creepy...

  • @pushingprimitives
    @pushingprimitives 2 ปีที่แล้ว

    Gatsby is great when it works. I’ve had a site working great, woke up the next day and it isn’t working…because reasons. Delete package-lock. Delete node_modules. Maybe get it working again. Maybe.

  • @jeffreytgilbert
    @jeffreytgilbert 2 ปีที่แล้ว +4

    After digging into gatsby, i can confirm that my only interest was in the integrations

  • @arturamorfati
    @arturamorfati 2 ปีที่แล้ว

    that stache thou🔥🔥🔥

  • @andresgutgon
    @andresgutgon 2 ปีที่แล้ว

    My theory, aqurire-hire

  • @netronominom2850
    @netronominom2850 2 ปีที่แล้ว

    We want blonde mustache too

  • @killerdroid99
    @killerdroid99 2 ปีที่แล้ว

    Yo man Theo you are looking like a freedom fighter tbh

  • @taufiqdev
    @taufiqdev 2 ปีที่แล้ว

    NOT THE STACHE!

  • @VipulSolanki-l2w
    @VipulSolanki-l2w ปีที่แล้ว

    You look like Joffrey Baratheon

  • @xWe2s
    @xWe2s 2 ปีที่แล้ว

    aaaaah my gaaaad, mustache.. UM NO, MAN, NO.
    LOL

  • @danvilela
    @danvilela 2 ปีที่แล้ว

    Like in the movie, bro die in the end

  • @otockian
    @otockian 2 ปีที่แล้ว +1

    Gatsby was so overhyped, I remember using that for a while and what massive, MASSIVE pain in the ass that thing was. When NextJs came about I never looked back, and I will never understand why anyone would use Gatsby today with so many significantly better options. Mind boggling. But I also don't understand why anyone would use Netlify today with so many better options, either so I guess there's that.

    • @danvilela
      @danvilela 2 ปีที่แล้ว

      They did a pretty big marketing for it back then. I was seeing it everywhere.

    • @verified_tinker1818
      @verified_tinker1818 2 ปีที่แล้ว

      What are some better alternatives to Netlify? (Genuine question; I'm new to the web dev space.)

  • @Gaijin101
    @Gaijin101 2 ปีที่แล้ว

    Theo becoming Stalin of JS xD

  • @Chris-cq3by
    @Chris-cq3by 2 ปีที่แล้ว

    dye the stache, dooo it

  • @muradbashirov6435
    @muradbashirov6435 2 ปีที่แล้ว

    nice mustache

  • @kamalmohamed6611
    @kamalmohamed6611 2 ปีที่แล้ว +2

    I feel satisfied when somebody talks how bad is gatsby 🙂🙂

  • @TaraBryn
    @TaraBryn 2 ปีที่แล้ว

    I tried gatsby for like 5 mins and thought it was super clunky. I then tried astro and it's not without it's issues, but is imo a lot smoother than gatsby

  • @onuralkan190
    @onuralkan190 2 ปีที่แล้ว

    Mustheoche

  • @Salafrazz
    @Salafrazz 2 ปีที่แล้ว

    MOUSTACHE!!

  • @julianfbeck
    @julianfbeck 2 ปีที่แล้ว

    love the fake stache

  • @AnshulM
    @AnshulM 2 ปีที่แล้ว

    it's better than astro for a static site with a tad bit of functionality (plain html and css sites are too boring). T3 all the way for dynamic though.

  • @MeekoEdits
    @MeekoEdits 2 ปีที่แล้ว +1

    nice {{, looking good

  • @wiztek1197
    @wiztek1197 2 ปีที่แล้ว

    What is on your face man

  • @luxusAI
    @luxusAI 2 ปีที่แล้ว

    nice fakestache

  • @techworld3043
    @techworld3043 2 ปีที่แล้ว

    Second

  • @gauravchauhan1645
    @gauravchauhan1645 2 ปีที่แล้ว

    I'd like to express my thoughts regarding the recent changes in your appearance. While I understand that you are free to present yourself as you please, I find it distracting and, quite frankly, a bit unsettling. As a long-time subscriber, I have to say that I prefer your previous look over this recent change. It detracts from the valuable content that you produce, and I believe that a JavaScript/TypeScript TH-camr should focus on delivering quality content rather than prioritizing appearance.

    • @packratrust
      @packratrust 2 ปีที่แล้ว

      Just listen to the video instead of watching if it bothers you that much

    • @everyhandletaken
      @everyhandletaken 2 ปีที่แล้ว

      @@packratrust I assumed their comment was sarcasm… but after reading again, I think he is serious.. wtf? 🤨

    • @gauravchauhan1645
      @gauravchauhan1645 2 ปีที่แล้ว

      @@packratrust Yeah will do the same in future.

  • @crade47
    @crade47 2 ปีที่แล้ว

    SHAVE IT OFF TWINK

  • @nextfangtechlead6239
    @nextfangtechlead6239 2 ปีที่แล้ว

    Cus Leo Dicaprio comes with it, duh! 🥸