3 ms·
> Doing ORMs and auth without knowing what you're doing imply a huge risk out of itself, which Go tries to avoid. And implementing it yourself the wrong way is
by aikah 10y ago
> Doing ORMs and auth without knowing what you're doing imply a huge risk out of itself, which Go tries to avoid.
And implementing it yourself the wrong way is also a huge risk.
- mixedCase 10y agoExactly the point I explained. You have to learn how it's done rather than try to look for a way out. The solution is not to have a magic tool that allows you to poorly work around the problem until it doesn't.