4 ms·
May have changed, but when I tried it, the first day with Flask was incredible. The second day, when you're ready to implement log-in and password pages, maybe
by digisign 5y ago
May have changed, but when I tried it, the first day with Flask was incredible. The second day, when you're ready to implement log-in and password pages, maybe email reset... you are on your own. There's six and a half third-party extension options with different overlapping scopes to research, the author of the best one has taken off for the Bahamas for two years…
- gen220 5y agoAh yeah, fair enough. The places I worked at-scale had their own o-auth setups (built mostly with FOSS) wired up to flask with some relatively small libraries [1]. I personally wouldn't want my web framework to implement login/password/email-reset for me, although I understand Django offers it to varying degrees. It's a space where "best practice" has evolved dramatically in the past decade. [1]: https://flask-oidc.readthedocs.io/en/latest/ https://flask-oidc.readthedocs.io/en/latest/ they looked a lot like this, fwiw. Although to your point, this too, hasn't been updated in 5 years. :)
- digisign 5y agoAs practice evolves, Django gives you a migration guide. That's great because the alternative could take a potentially unbounded amount of time. And you still could go it alone if sufficiently motivated. Although it could get annoying, as mentioned. The main point though is that I'm not interested in being on the forefront of login, it is not a differentiator (unless project is a laggard). In fact being five years behind bleeding-edge sounds a bit perfect.