kjz
kjz
Redesign: Everything Broke – Oh my, this sounds a nightmare. Robin Rendle on changing static site generator, from 11ty to Astro. I’m sure this will be fixed eventually but it means I have to cautiously [my emphasis] make any change, no matter how small. Change the markup, watch the ... www.thisdaysportion.com
|
Embed
pimoore
pimoore

@leonp I’ve even read a few places of Hugo making breaking templating changes in the past, though I don’t know the specifics of what those were. I don’t know how common these issues are in something more seasoned like Jekyll.

|
Embed
kjz
kjz

@pimoore I think Hugo’s pretty stable and Jekyll never changes any more, for better or worse. My gripe is more with something like Astro introducing a complex build process and javascript frameworks just to produce a simple, static site.

|
Embed
pimoore
pimoore

@leonp Did Jekyll ever get their incremental regeneration off the ground as a full feature, or is it still experimental? That was always the biggest beef people had with it; slow build times.

|
Embed
In reply to
kjz
kjz

@pimoore Yeah, it works, and makes quite a difference, but it’s still relatively slow. On my highish-spec MBP from 2016 my site builds in ~2s, which is fine. It’s still painfully slow on a large site, though, and you only use it on content pages. If you’re making design changes that affect every page you’re back to a standard build (about 5-6s on my website).

|
Embed
pimoore
pimoore

@leonp That seems to be Hugo’s biggest draw is the insane build speed, which I don’t think any other static generator even comes close to. I appreciate that micro.blog is using it on the backend for that reason.

|
Embed