Johnson Chu

I feel like we are on one of those pendulum swings right now where people undo a decades worth of work only to realize in 5 years they over swung because they missed the actual problem. We see this all the time. I'm not going to argue against imperative handles in all cases. But I want you think about the implications. If you unwind these things you remove guarentees. Like why do developers like Rust or TS? Its because through constraints certain classifications of issues aren't possible. The solution solves itself structurally. Structural constraints also have a nice property when composed. You keep benefitting from them as you layer on complexity. Build more constrained systems. Like if you aren't batching synchronous updates you probably have no foundation to managing async race conditions structurally. We shouldn't confuse incidental simplification(removing a problem) with structural simplification. Sometimes legitimately we don't need to solve certain things. The solution should fit the problem. But more often than not in a well established space we are just delaying the inevitable.