Brian Rinaldi is a Developer Experience Engineer at LaunchDarkly with over 20 years experience as a developer for the web. Brian is active in the community running CFE.dev and Orlando Devs.
I have a couple favorites depending on the scenario.
If I am building a site that doesn't have complex UI functionality that may require a framework (like React), I use Hugo. It's blazing fast and I have been able to do pretty much anything I want with it (for example, cfe.dev has login, search, etc. and it's all Hugo).
If I need complex UI functionality and want a framework, I go with Next.js. I like the way next handles things like routing and static props. The learning curve feels steep to me and I often feel like I am fighting difficult debugging related to client vs. server values, but those are just some complications of using a frontend framework for Jamstack sites, not specifically any issue with Next.
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.
I have a couple favorites depending on the scenario.
If I am building a site that doesn't have complex UI functionality that may require a framework (like React), I use Hugo. It's blazing fast and I have been able to do pretty much anything I want with it (for example, cfe.dev has login, search, etc. and it's all Hugo).
If I need complex UI functionality and want a framework, I go with Next.js. I like the way next handles things like routing and static props. The learning curve feels steep to me and I often feel like I am fighting difficult debugging related to client vs. server values, but those are just some complications of using a frontend framework for Jamstack sites, not specifically any issue with Next.