Gatsby is a static site generator. We needed SSR because we have a lot of content edited every day, aggregating data from various sources. I'll have to analyze gatsby to find an useful use case. For now, next.js accomplishes our needs.
Hey all! 👋 I’m Ryo, a Sr. Design Technologist at PlayStation. I do web dev with React/TS/Node and game dev with Unity/C#/C++/OpenGL/DirectX. Feel free to ask me any questions! 🤘
Yeah I end up using Gatsby for projects like documentation, or blogs, where there's a significant amount of static content.
It's not feasible for something like a community (like Dev.to), since you'd be re-building every time someone makes a small post/comment, or reading off an API client-side (thus not benefiting from SSR).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Did you happen to take gatsbyjs into account? I haven't been able to find much material comparing the 2 unfortunately but am very interested in both
Gatsby is a static site generator. We needed SSR because we have a lot of content edited every day, aggregating data from various sources. I'll have to analyze gatsby to find an useful use case. For now, next.js accomplishes our needs.
Yeah I end up using Gatsby for projects like documentation, or blogs, where there's a significant amount of static content.
It's not feasible for something like a community (like Dev.to), since you'd be re-building every time someone makes a small post/comment, or reading off an API client-side (thus not benefiting from SSR).