|
|
|
|
|
|
by cdaringe
2810 days ago
|
|
|
You are grossly simplifying the value that SSGs provide and problems they solve. Gatsby has some quirks, but it does strike a good balance of providing value whilst giving you plenty of control. It does the data capture and transformation of content I want, it gives me a place to explore and visualize those parsed datas, and it lets me control how to render that content in a context that very closely resembles the final artifact (jsx, html). It doesn't cram a new DSL down your throat (jsx is close to html enough, and, it's optional). It has excellent debugging in node and the browser. Hugo doesn't have those, Jekyll super doesn't have those, and everyone's home grown scripts certainly don't have all of those. There isn't a one-size-fits-all, but saying it's a poor tool because it has a lot of dependencies is silly and immaterial. |
|
|
Spend an extra day and build your own. It will fit you exactly. No more, no less.
> but saying it's a poor tool because it has a lot of dependencies is silly and immaterial.
You're missing also the time it takes to customize it. For example: https://github.com/gatsbyjs/gatsby/issues/4583
How complicated can it be to have simple tree navigation? Turns out, it's pretty complicated...
I could role my own in 20 minutes without the abstractions, but no, I'm fighting uncessaray abtractions/layers/tooling that gives very little value when it comes to converting .text -> .html.
It blows my mind that people don't see this.
Read this: http://tonsky.me/blog/disenchantment/