The reality is closer that, state should be immutable, and minimized as much as possible, but at the end of the day, almost every interesting problem requires storing state. Once you reach that point, classes are simply a better solution for state than closures. Especially if your class and its variables are immutable, you get all the benefits I mentioned and none of these tradeoffs. Your state is explicitly stated.

The high expenses of the bay area are a policy choice by the local and state government to disallow investment. As such everyone is competing for the same old housing stock and office space that cost a 1/3rd of what it does now years ago. In effect, house owners and landlords are appropriating tech profits to themselves.

I hope the banning of single home zoning in California helps to alleviate this issue.

The reason no other explanation makes sense to me is that any purely market based explanation, like energy or China, we would see a corresponding drop in US labor force productivity, but the whole point is that that productivity did not drop.

One question i have for you is, why didn’t the union just fight the cuts? A union is not a nicety granted by the corporation, its whole reason to be is to fight corporate power when needed. It sounds to me like that union was already made powerless by the time the crisis occurred.

You can see union membership was on the decline since the 1950s, but it accelerated around the 70s. It is hard to see the timeline in that graph, in this one it is harder to see the acceleration, but it is easier to see the timeline: https://rpubs.com/jncohen/uniondensity

For some kinds of monads, like maybe, that’s all you need.

But, some other kinds of monads need more logic. List is one, IO is another.

In OOP language, sometimes all you need is the parent class. But sometimes you need to extend the parent and add more.

Shameless plug for my own article that did something similar about a week ago: https://medium.com/@ameltzer91/an-easy-to-understand-monad-g...