multithreading

When multithreading means that incrementing/decrementing a reference count is no longer deterministic, you need locks, or all hell breaks loose.

As to multithreading, first since when is a web server the be-all-end-all of multiprocessing?

Hell, you don't even need multithreading to do a webserver, just use Unix processes.

Yes, to a certain degree multithreading is hard, but it's not rocket science.

Chrome runs each tab in its own process- also not multithreading.

But I think that main reasons why you should switch are multithreading and Java libs.

Multithreaded programming is not inherently more complicated than everything else, but finding bugs caused by multithreading is inherently more difficult than finding any other kind of bug.

Over the years the language differences between Clojure & ClojureScript have more or less been erased beyond very host specific details like String methods, no multithreading, etc.

No gpu-compute, no shared-state multithreading.

If anything, I believe it might be the other way around, since holding a CS degree means you've had a FP course and you're more aware of the implications of multithreading, immutability and side effects.

On multithreading, though, I think you're off base.

This is the part most software engineers are not used to -- you move the operations to the threads that own the data rather moving to the data to the threads (traditional multithreading) that own the operations.

You get one guy, who is seemingly very smart, and he says basically "Don't do multithreading, it's very hard.

"Don't do it!" is one way of proving that multithreading bugs don't exist.

Multithreading is somewhat unsafe in general.