Our great sponsors
-
> In Go, you can build massive projects without needing any dependencies to make error handling ergonomic.
are we talking about the same go where the average code looks like this, a big long chain of if blabla return nil, err ?
https://github.com/cockroachdb/cockroach/blob/5fb4478b94ecaf...
like, code like this is exactly the reason why exceptions were invented
-
> It's not like there's likely hidden segfaults or memory vulns waiting there…
It's funny you mention that, because the now-deprecated 'failure' crate has such a memory-safety vulnerability: https://github.com/rust-lang-deprecated/failure/issues/336
Granted, consuming code is only vulnerable if they opt-in to implementing a provided trait method that most people should never ever need to implement. But I would still try to eliminate 'failure' from my dependency graph if possible (and I recently submitted PRs to two dependencies I was using to remove 'failure' from _their_ dependencies).
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Related posts
- Linux surpasses the Mac among Steam gamers
- rage - a minimalistic load testing tool
- Eli5: Why do companies use the products of Oracle to store information, when they can just use spreadsheets like Excel, or make their own spreadsheet software?
- NextJS is fullstack, why some people use it only for frontend and how can you use it in fron end ?
- Defer your mutex unlocks