mj's Logbook

Tag: programming remove

A Programmer's Introduction to Mathematics

Recommended by Keith Peters

books programming math

2 months ago

Let's create a basic CRUD with Rust using tide

rust tide programming web tutorial

3 months ago

The Little Book of Rust Macros

rust macros books programming

3 months ago

Malleable Systems Collective

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

programming design tools

7 months ago

Learn Go with Tests

books programming golang

7 months ago

Carp

languages programming lisp carp

7 months ago

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.

programming ocaml advice

10 months ago

Tools for Thought

Tools For Thought by Howard Rheingold

books programming technology

10 months ago

Git Flight Rules

git programming

1 year ago

Bevy

A data-driven game engine for Rust.

programming gamedev rust gameengine

1 year ago

PostgreSQL Exercises

postgres tutorial programming database

1 year ago

Rust Resources

rust programming

1 year ago

Elegant Library APIs in Rust

rust programming

1 year ago

Introduction to Networked Physics

gamedev games programming network

1 year ago

Gerbil Scheme

“Gerbil is a meta-dialect of Scheme with post-modern features”

programming scheme lisp language

1 year ago

Learn ClojureScript

A ClojureScript book

clojurescript clojure books programming

2 years ago

Nand Game

Build a game out of nand gates.

programming cs games tutorial

2 years ago

Processing Sphere

processing programming

2 years ago

How to Manage HTML DOM with Vanilla JS

html programming javascript

2 years ago

Pixel Vision 8

A fantasy console with a more graphical bent and swappable constraints.

pv8 retro fantasy console games programming

2 years ago