peppery-idiot

You can do a lot of the codeblock stuff with JavaScript's Function prototype (bind, apply, call):

const someBlock = function () { console.log(this.a + 2 + this.c); }

const myFunc = someBlock.bind({a: 1, c: 3})

myFunc(); // => 6

Their future success is heavily tied to that set of opinions being correct and drumming up further investment. Even with the best will in the world, this type of quantitative opinion will be hugely positively biased.

They are CEOs, half the job is public cheerleading.

From my limited knowledge, Rust's type system is quite close to the ML family-- so perhaps F# would be a general-purpose GC'd language equivalent?

I am mainly interested to know how much overhead time is spent appeasing the borrow checker and managing memory that would otherwise free up mental cycles if a GC were available . The async story for Rust also seems confusing (but I hold my hands up and plead ignorance on this count).

For web work, are there benefits to using Rust over a garbage collected language that also benefits from a similar type system?

Yes, if you're an application developer that has to build the latest feature to come out of a spin-the-wheel product management meeting. E.g., you're tasked with adding arbitrary custom PDF functionality to your web app. For the majority of tasks, there are Clojure libs but if you need it Java has battle-tested libraries to do all of the tedious (/s) things that keep business-people happy. You can't assume the same for smaller languages/ecosystems.

I was under the impression OOP with classes is not cache performant when doing common game engine tasks like mass updating the velocity or position of objects.

Our industry has a few standard formats that we rolled our own for. It was a relatively large amount of work.

Three month notice periods are relatively common in the UK, don't worry about it -- and don't quit before you have another job lined up.

Your proposed course of action is predicated on a hypothesis, that no employer wanting to make you an offer because of your notice period, that has no supporting data. Anecdotally, nobody worth working for (and plenty of companies not worth working for) care about a 3 month notice period.

I'd say put the feelers out there and interview casually for a while before writing yourself off because of your notice period.

Also, I don't know if other commenters are based in the USA where it seems common for employers to practice retaliatory firings.

In the UK if you have more than 2 years of service at your current employer, it's very very unlikely that they can fire you without a negligence/misconduct claim against you. You're more likely to be put on paid garden leave, or somehow made redundant (but you should be paid a lump sum).

Yeah, it's great

Biodiversity is not about enjoying nature. It is key to the stability of how humanity currently lives on Earth.

The term to research for why biodiversity is useful in a utilitarian anthropocentric way is "Ecosystem Services".

The only way we know how to keep what we have is with biodiversity.

I don't think anyone who uses Clojure in anger would put it on the same level as JavaScript when it comes to letting through a ton of runtime errors. The integrated tooling around editors, clojure.spec and the REPL is very good at curtailing the downsides of dynamic typing.

I disagree on Clean Code. It puts too much importance on superficial "5 easy steps" points that put too much priority on the wrong things. Reading quality open source code is a better way of getting that understanding IMO.

Pretty much everything in CI is driven by YAML or JSON or YAML string as a value in a JSON property and they uniformly suck.

So I think GP is correct.