Gatsby static‑site framework criticized for JavaScript bloat and heavy dependencies

A developer reports migrating away from the Gatsby static‑site framework, citing excessive JavaScript and JSON payloads and a large number of dependencies as major drawbacks. Performance testing showed a three‑fold reduction in network requests and data transferred after leaving Gatsby. The author notes that while Gatsby can deliver fast pages, the underlying architecture adds unnecessary overhead.

Another piece outlines Gatsby’s core concepts, describing how the framework pulls data from varied sources via GraphQL, uses Node.js for page generation, and relies on React for the UI. The article provides illustrated notes on Gatsby themes, the JAMstack, and the distinction between page and static queries, aiming to clarify the framework for beginners.