|
|
|
|
|
by lelandbatey
2053 days ago
|
|
I find that this is a totally fine trade off to make until it isn't, and by then you're completely confined by your choice of framework. Better to use libraries built to compose around interfaces taken from the standard library so you lose none of the control. I'll also emphasize that doing it this way does make discovering the initial pieces harder than if they're all in one framework together, but I find the slight increase in research yields orders of magnitude improved results once your code starts to age past the two year mark and you reap all the reliability and composibility of the standard library. Also, here's a list of out-of-the-box library implementations for all the features you mentioned: Sessions: https://github.com/gorilla/sessions CSRF: https://github.com/gorilla/csrf User auth: https://github.com/qor/auth |
|