dwyl / dwyl/abase

Why? (Is this needed? Are we "Re-inventing the Wheel"...?)

Open
#25 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
9
Forks
0
PR merge metrics
No merged PRs in 30d

Description

## tl;dr
### Why is this _Needed_?

This is not the _first_ system people can use as the "base" for their apps.
#### "out-of-the-box" / "off-the-shelf" User registration/management systems:
- https://github.com/braitsch/node-login [no tests]
- https://github.com/jedireza/aqua looks _good_ but not focussed on _simplicity_
#### Backends for "Modern JavaScript Apps" >> ["_Assume a can opener_"](https://en.wikipedia.org/wiki/Assume_a_can_opener)

There is _no shortage_ of frameworks that _clame_ to "_solve_" the problem of helping people build web applications
- Firebase (Google Backend-as-a-Service) - https://firebase.google.com/ includes user reg/auth and admin.
- Meteor - https://github.com/meteor/meteor
- Hoodie - http://hood.ie/about/
- Horizon - https://github.com/rethinkdb/horizon
- Deployd - https://github.com/deployd/deployd
- Sails - https://github.com/balderdashy/sails
- deepstream - https://deepstream.io/

All of these frameworks have one thing in common: they _**totally ignore Progressive Enhancement**_ 😞

> read: https://gdstechnology.blog.gov.uk/2016/09/19/why-we-use-progressive-enhancement-to-build-gov-uk/

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.