Actually it's very controversial if we should spend marginal resources on deworming. It may have very large economic benefits, but the evidence isn't clear (https://unherd.com/2020/08/what-worms-can-teach-us-about-the... has some details).

I agree that dune is worse in many important ways than the build systems of languages like Rust and Go (where they were developed at the same time as the language, rather than 20 years later). But dune config files aren't lisp. They're s-expressions, which have the same syntax as lisp but are just static data like json/yaml/toml (and once you get used to them, I think most people prefer them to those).

It's fine to trade when you know something that the general public doesn't. Indeed that's really the only time you should trade: you presumably want to make a profit, and society wants relevant information to be incorporated into prices. The thing that's not fine is trading on secret information that belongs to someone else. Insider trading is about theft, not fairness. https://www.bloomberg.com/opinion/articles/2015-04-01/anothe...

I believe Ruby and OCaml have both anonymous positional arguments and keyword arguments with punning (i.e. `f ~arg` expands to `f ~arg:arg` in OCaml).

You can get those cool features in languages such as OCaml/F#/Scala/Haskell, and then you don't have to worry about managing memory because you have a GC.

Sure but all of them are weird. Rust is something you can pick up in an afternoon if you have expeirience in C++-like languages.

From the point of view of somehow that has taught C++ as TA, worked with C and C++ during several years in some heavy contexts, an afternoon won't do it.

It is quite possible that an Erlang dev billing 3x more than a PHP dev will be more than 3x as productive.

There is an interesting take on command-line code review from Jane Street here https://blog.janestreet.com/putting-the-i-back-in-ide-toward...

Adding cr comments as actual comments in code is a really interesting take on code review. Never seen that before.

Me neither! I at first thought "hey, that's cool", but then I realized that the replies would also have to be in the code, and then it's no longer as appealing to me. And what do you do if you want to have a back and forth discussion? Take it "offline"?

Unit tests and "type systems" have very little in common with Kubernetes and GraphQL.

Also, GraphQL is not complex. You can learn the basics in an hour or so.

It's interesting that they have a much higher valuation (and from some cursory research, moderately more users) than Depop, despite (AFAIK) being completely obscure in the US/UK.

There are various universities that teach Haskell or similar languages in first year.