đź”± One step after vanilla javascript, one step before frameworks.
I've got tired of js frameworks, so I will start to experiment with different js stacks. composing libraries is more fun than learning oppinionated frameworks. At the end, I would have the basic experience and maybe some benchmarking to make some decisions.
If there are already a lot of js framework choices, there is even more js libraries. So, I arbitrary selected some of them and mixed in this repo, accross different project folders. Every folder is supposed to be the same app, only changing the js stacks, so, there are some common files. Also, there is only one folder for benchmarking, as the same test would be applied to every app.
The app is a simple blog, with common css files. The state model must support posts with comments, and manage routes to visualize them. The routes are:
/posts
/posts/:post_id
/posts/:post_id/commentsThe model structures are:
const post = {
title: '',
date: {},
content: '',
author: '',
comments: []
}
const comment = {
author: '',
content: '',
date: {}
}The actions for the state container are:
const ADD_POSTGo to each one of the following folders to check the implementations
- yo-yo + sheetify + send-action + sheet-router
- yo-yo + sheetify + send-action + director
- yo-yo + sheetify + redux + sheet-router
- yo-yo + sheetify + redux + director
- yo-yo + cxs + send-action + sheet-router
- yo-yo + cxs + send-action + director
- yo-yo + cxs + redux + sheet-router
- yo-yo + cxs + redux + director
- hyperscript + hyperx + sheetify + send-action + sheet-router
- hyperscript + hyperx + sheetify + send-action + director
- hyperscript + hyperx + sheetify + redux + sheet-router
- hyperscript + hyperx + sheetify + redux + director
- hyperscript + hyperx + cxs + send-action + sheet-router
- hyperscript + hyperx + cxs + send-action + director
- hyperscript + hyperx + cxs + redux + sheet-router
- hyperscript + hyperx + cxs + redux + director