Jekyll, Netflix, ZAC discussed on ShopTalk
Besides each other at an end complementing each other. And then there's this interesting hybrid of creating elect largely static site generated site, but then when static site generation starts becoming impractical. Like, you have a ecommerce site with ten thousand products in your Jekyll build takes an hour, or whatever it is. You don't have to do it that way. You can step excite generate sixty percent of the site and then have slash product which has like some query parameters that hits an API for. The data that isn't a cloud database somewhere. You know, you can kind of be half-and-half, which is so cool. Yeah. I would I I mean, maybe they got into this. But I would just love to see like a I don't know like a blog post in architecture blockbusters kinda hard because they're so specific to some implementation type of site. But like, I don't know I'm thinking like I built a big dumb like ecommerce site as a static website like, you know, ten thousand products or something urban outfitters right now a static site or something like that would be like. Oh, no. That would just be like, so interesting. I don't know if it's been done or I don't know like what the scale is. Because in my mind, always like oh status. I that's small that small that's for small. But like you're saying, it doesn't have to be like, you know, you can just. There was a part of the keynote was very interesting, and how you can you don't have to stop your current server side architecture in which to dabble your feet in this which is fascinating because you know, some of the best technologies out there are ones that allow for incremental adoption as they say, you know, I think in a way that's you could attribute some of the success of react to that is that you don't necessarily have to go all in on all your entire architecture to use some react in your app now. Whether that's true for your app, or what I think it's generally true industry-wide in so part of this demo was that. Specifically has this kind of proxy feature on a URL by URL basis. Meaning that you could spin up unedifying sight and say like this particular URL is going to is going to be statically served through Netflix lab, none of the rest of it is or something. Yes. You can be like, okay. I see like if I wanna run part of my app, or you know, some sub directory of eyesight kind of static hosted style you can't. And then proxy the rest of it to wherever it's the rest of it is being served already. So you could dip your does. Yeah. No. That'd be just curious like how far people have pushed it, you know. But that's it. There's also, you know, even in the static site world. A lot is kind of changed. I mean, I still use Jekyll. I love Jekyll IVA weird like partisan point of view and Jekyll, but you know, like. Zac, leathermans eleven apparently is like all the same features as Jekyll in like, you can even bring your own tempting language, and it eleven d just spits out websites. And I'm like well. I mean, those seem like no you notice more appealing to me than ruby for whatever is kinda who cares because it's just static. You know, like, what is a matter. Really? But I feel like if I had to hack on it. I could I'd be more useful. And I guess you're kind of a ruby assed anyways, comfortable hacking either way. Yeah. I mean, I don't know. I I'm also in the like try not to hack core camp..