gedhrel

Eh? You might suggest it's another reason why persistent (aka immutable) data-structures have merit; but this is raw pointers.

He's certainly pretty impressive.

The originals were much better. Lara Croft was a jet-setting dilettante with Girl Power from the era of "Cool Britannia" and the Spice Girls.

Comparatively, the reboots are utterly po-faced.

The issue here is that the author of that post, and potentially the fictional author of the thing being lampooned, are not drawing a distinction between a tutorial (or an explanation) and a how-to.

https://diataxis.fr/

Either you want to get a task done, or you want to spend a lot longer learning how to work that out for yourself.

(Many tutorials will include small set of how-to-like instructions because emulating the actions of a master will improve one's vocabulary of what can be done as well as how it is achieved.)

Start with the core gameplay loop. Look for the fun. Look for what you can take out, not add.

Play-testing something like this with pencil and paper first might be a good idea. Once you work out why it always plays the same way, then you can look for how to perturb the gameplay.

What a twat.

Erlang wasn't the first implementation of CSP.

Clojure has it's own set of idioms; it comes with some small surprises for old lisp hands. There are some things it's really brought into the mainstream: performant persistent data structures in particular.

As well as excellent tooling and pedagogy, the principle attraction of Racket is the macro system. There's a great book about this (this is true of just about all aspects of Racket). Racket's focus is on building a tower of languages via macro extension. Metaprogramming is thematically FP-adjacent but neither sufficient or necessary; but if you're looking for a fun learning experience it's really worth a look.

In terms of employment opportunities - I know of several Clojure shops (on the JVM it has the bonus of being able to take advantage of the hole ecosystem), but I'm not aware of anywhere that's using Racket outside of the academic sphere.

Another great avenue into this world is Racket. The tooling is fantastic and the documentation culture is first-class.

I've a couple of GP friend who used to describe "Dr Google" as their online colleague.

The point being, they were somewhat trained in interpreting risk as opposed to the stereotypical googler-of-symptoms. Once upon a time search engines were quite useful.

I'd go with Erlang over elixir, but it sounds like you already have an interest in gleam.

FWIW: just pick one and get started. There are some major axes to consider: pure versus impure, lazy versus strict, static versus dynamic typing, but to kick off if you've done no FP before it's probably better to just go for it.

There are some really intriguing "next steps": SICP, the ML module system, the Haskell ecosystem, the OTP approach to state, but to begin with it's just worth getting used to some basics.

Yes. And "Lego" is the collective noun.