Let's create a basic CRUD with Rust using tide

rust tide programming web tutorial

07/14/2021

The Little Book of Rust Macros

Malleable Systems Collective

Promoting malleable systems (programs/solutions that can be changed by the user).

Learn Go with Tests

Carp

sexprs
no gc/vm
inferred static types
functional interface, mutable under the hood
folks seem to be using it mostly for games so far?

language programming lisp carp

03/04/2021

Passerine

"A small extensible programming language designed for concise expression with little code."

Keep an eye on this.

Choosing an Error Handling Strategy

From Real World OCaml. The whole page on error handling is good, but I'm mostly interested in Exceptions vs explicit Result/Error types:

Given that OCaml supports both exceptions and error-aware return types, how do you choose between them? The key is to think about the trade-off between concision and explicitness.

Exceptions are more concise because they allow you to defer the job of error handling to some larger scope, and because they don’t clutter up your types. But this concision comes at a cost: exceptions are all too easy to ignore. Error-aware return types, on the other hand, are fully manifest in your type definitions, making the errors that your code might generate explicit and impossible to ignore.

The right trade-off depends on your application. If you’re writing a rough-and-ready program where getting it done quickly is key and failure is not that expensive, then using exceptions extensively may be the way to go. If, on the other hand, you’re writing production software whose failure is costly, then you should probably lean in the direction of using error-aware return types.

To be clear, it doesn’t make sense to avoid exceptions entirely. The maxim of “use exceptions for exceptional conditions” applies. If an error occurs sufficiently rarely, then throwing an exception is often the right behavior.

Also, for errors that are omnipresent, error-aware return types may be overkill. A good example is out-of-memory errors, which can occur anywhere, and so you’d need to use error-aware return types everywhere to capture those. Having every operation marked as one that might fail is no more explicit than having none of them marked.

In short, for errors that are a foreseeable and ordinary part of the execution of your production code and that are not omnipresent, error-aware return types are typically the right solution.