Why you should consider using GatsbyJs? (compared to Frontity)
1. The Speed
but a good caching system is needed. Something that we still need to figure out (find good choices, easy ones and properly explain them). Right now it is solved with Vercel and it will be properly solved soon w/ embedded mode.
2. The Plugins
In Frontity this would the equivalent of packages. The backbone to create packages is done but we still need to:
- properly explain packages philosophy
- encourage people to create packages
- create more packages ourselves
3. Starters & templates
Gatsby has a lot more starters and templates. We need to encourage people to create more templates and we need to find a better system to organize them and make it easy for people to find them and use them
4. The rise of the Jamstack
I think here we can explain better where is Frontity located regarding JamStack.
5. ReactJs based
Frontity apps are isomorphic
Gatsby apps are Static Generated sites
The code served to the user is similiar but Frontity one is generated in runtime and the Gatsby one is generated in build time
6. Ease of use with Markdown
Frontity is not meant to be used with Markdown
7. SEO
With proper architecture SEO is as good.(better?) as with a Static Generated Site (Gatby)
Why should you avoid Gatsby? (compared to Frontity)
1. Increasing build times
Here Frontity offers a clear advantage over Gatsby
2. Completely Dynamic website
I don’t fully understand this point as w/ Gatsby once the site is “hydrated” you should be able to make it as dynamic as you want (requests from different API’s, behaviours,…)