3 ms·
In a dozen of hours I wrote Sitio[1]. Sitio generates static pages with React templates and if wanted they also become alive React components at the client. It
by fiatjaf 7y ago
In a dozen of hours I wrote Sitio[1]. Sitio generates static pages with React templates and if wanted they also become alive React components at the client. It has a simple imperative API, no GraphQL, no Webpack, any kind of datasource can be easily plugged (in fact I did plug many).
It turns out Gatsby also exposes an imperative API that runs behind its fancy declarative API, and it's very similar to mine.
However, I wrote mine in 12 hours. Gatsby has a big team and millions of dollars and it's been in the works for many many years.
And still some weeks ago I tried to use Gatsby to generate a site with data from Trello and Instagram and couldn't, hit some bugs, but mainly hit an opaque and very complex API.
Why?
[1]: https://github.com/fiatjaf/sitio https://github.com/fiatjaf/sitio
- dplgk 7y agoNo webpack is a big win. Thinking Gatsby is this fun & easy thing and then realizing you're going all-in on the current npm/JS insanity is not a good feature.
- fiatjaf 7y agoI have this great badge at the repository: [Webpack free] https://camo.githubusercontent.com/fdcb107fde40edb15afb7e80f64349fa4fe7c11b/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f7765627061636b2d667265652d6f72616e67652e737667 https://camo.githubusercontent.com/fdcb107fde40edb15afb7e80f...
- fiatjaf 7y agoWorse: all the datasources were provided by plugins written by third-party indie developers working for free (and for that reason they weren't perfect, of course). What is the core team wasting their time on?