There's a proliferation of dynamically and/or softly typed languages. There are very few, if any, truly untyped languages. (POSIX shells come close, though internally they have at least two types, strings and string-arrays, even if the array type isn't directly usable without non-POSIX features.)

Do you mean Dan Luu, or one of the studies reviewed in the post?

Yeah, I understand that Option and Maybe aren't new, but they've only recently become popular. IIRC several of the studies use Java, which is certainly safer than C++ and is technically statically typed, but in my opinion doesn't do much to help ensure correctness compared to Rust, Swift, Kotlin, etc.

What virtual desktops do you prefer? I don't find Mac OS's significantly better, and I haven't spent much time with very many Linux window managers other than i3 (and that was years ago).

I think it really depends how much time you actuall spend working on these temporary systems, and what mechanisms are available for automatically configuring those systems, even temporarily. You can generally assume that some version of bash is available on all systems, so if you have a bashrc that you like, you could use sshrc or kyrat to at least bring over some functions and aliases (I used sshrc long ago but haven't tried kyrat): https://github.com/cdown/sshrc, https://github.com/fsquillace/kyrat

If you do want to use nushell on remote systems, possibly xxh would enable that; I haven't used it personally, but it looks promising: https://github.com/xxh/xxh

If you're not using ssh, then it really depends what you are doing.

My point is that the claim in the comic and in other comments that this corrupts your repo or loses work simply isn't true.

Isn't your objection there basically "LF doesn't pay enough for people to put up with negative social dynamics"? In which case, wouldn't paying more help a lot?

There were memory-safe languages long before C was invented, though; C was widely considered "dangerous" even at the time.

Genuine question: if you're writing a new CLI utility, why not Rust? This is arguably where Rust has most excelled, most famously with ripgrep.

How is that easier? It doesn't look like it provides a list of which modules have a __name__ == "__main__" block.

OCaml seems really close, but I'm told that there are problems with its concurrency story. I do think it sounds like a really good language.

Thanks for sharing the interview with Lattner; that was quite interesting.

I agree with everything he said. However, I think you're either misinterpreting or glossing over the actual performance question. Lattner said:

The performance side of things I think is still up in the air because ARC certainly does introduce overhead. Some of that’s unavoidable, at least without lots of annotations in your code, but also I think that ARC is not done yet. A ton of energy’s been poured into research for garbage collection... That work really hasn’t been done for ARC yet, so really, I think there’s still a a big future ahead.

That's optimistic, but certainly not the same as saying there are no scenarios in which GC has performance wins.