You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2017. It is now read-only.
Aleph is going through a redesign process. As part of the effort, we will be updating the UI of the product.
Currently, Aleph is using the Angular 1.x framework for the UI. Due to maintenance issues, we decided to move away from Angular and we are considering a modern alternative to it. The decision should be based on the following aspects:
community support and the maturity of the project
the maturity of the tools for testing, deployments and QA
learning curve
Related to the framework choices, we are exploring any UI components framework/toolset/addons that can play well with it and potentially reduce the boilerplate to speed the delivery times.
Currently, I'd propose:
React
Redux
Bootstrap 3 or 4
I've had a very quick look at MobX, which seems pretty magical but fundamentally does the same thing as Redux. I don't have strong feelings either way, other than all other things being equal, I'd much prefer adopting a widely used and maintained JavaScript library than one that is not, i.e. does MobX mean that components made by us can only be used in a MobX-based app and that those re-usable components out in the React ecosystem that assume Redux will be inaccessible to us?
The text was updated successfully, but these errors were encountered:
Aleph is going through a redesign process. As part of the effort, we will be updating the UI of the product.
Currently, Aleph is using the Angular 1.x framework for the UI. Due to maintenance issues, we decided to move away from Angular and we are considering a modern alternative to it. The decision should be based on the following aspects:
Related to the framework choices, we are exploring any UI components framework/toolset/addons that can play well with it and potentially reduce the boilerplate to speed the delivery times.
Currently, I'd propose:
I've had a very quick look at MobX, which seems pretty magical but fundamentally does the same thing as Redux. I don't have strong feelings either way, other than all other things being equal, I'd much prefer adopting a widely used and maintained JavaScript library than one that is not, i.e. does MobX mean that components made by us can only be used in a MobX-based app and that those re-usable components out in the React ecosystem that assume Redux will be inaccessible to us?
The text was updated successfully, but these errors were encountered: