When you have large transfers of wealth and the wealth gap grows significantly the only thing for rich people to do is buy up assets. Assets are fixed, so the share of assets owned by rich people are drastically increasing. This is inline with the # of houses owned by private investors and #'s of assets owned by other investors will reveal the same thing.

Maybe for companies (although I'd argue it's extremely bad there as well), but for Governments this is a terrible idea!

Remember that "probationary" doesn't mean new. I just learned this, but apparently when getting a promotion it puts you back into the "probationary" period at your new role. So people with 10+ years of service are being let go because they had recently been promoted.

I will say that Ford has drastically improved in the last few years (I own a fairly new Explorer ST) but much of what they've done you can clearly see is copying what Tesla has done. Even still it is miles away from what Tesla has done.

As far as ICE companies competing, most of what we've seen so far is fairly limited and there is good reason for this. Their whole profit model is built on the dealership model and serious investment into electric cars is going to, essentially, nullify that model of doing business. Moving to electric cars is not just an incremental changes for current large automobile companies but an entire paradigm shift in how they do business.

Either way, for scripting uses there are tools like babashka or lumo with sub second startup times.

You mention zoning laws in particular. Those were designed for specific reasons so what about them would you change? Surely you aren't suggesting just to get rid of them all?

Your examples of the type safety can all be mimicked with spec in Clojure. Granted spec is opt-in (but I'm guessing so is some of the more detailed type safety attributes you are talking about like NonEmpty).

Anyhow, to each their own and one persons experience isn't likely to be the same as the others so I'd encourage everyone to try out many languages. Some languages click with people more than others do so it's always worthwhile to experiment.

I would suggest that if you have runtime bugs popping up in Clojure programs then that would suggest the inputs to functions (since they should be primarily pure) are not being validated which can easily be accomplished. I would imagine this needs to be done in Haskell as well since just verifying types does not indicate valid data.

Primarily been developing with Clojure for 5 years now with some pretty large codebases. It does depend on how you write your code but favoring pure functions, pushing immutability to the edges of your programs allows you to refactor without fear.

Clojure also has many things to aid in this such as pre/post conditions, clojure.spec (which allows you to build complex type definitions), and of course test.check (property based testing).