3 ms·
Doing ORMs and auth without knowing what you're doing imply a huge risk out of itself, which Go tries to avoid. If you have relational data the solution is not
by mixedCase 10y ago
Doing ORMs and auth without knowing what you're doing imply a huge risk out of itself, which Go tries to avoid.
If you have relational data the solution is not to use an ORM to half-abstract it away, it's to learn SQL. ORMs can be useful tools to avoid boilerplate, but they will show their ugly internals when SHTF, and those are always harder to understand than plain SQL.
As for auth, it's very easy to add to any web application or HTTP API using one of the many middleware solutions out there.
- 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.