New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open

nelsonic opened this issue Sep 22, 2016 · 0 comments

Member

nelsonic commented Sep 22, 2016 •

edited

Loading

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"

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/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment