shthrow

How is it a good idea for every user interaction to hit the server?

Correct, but that is the same for any kind public API though. However that is slowly starting to change with statically typed APIs like GraphQL and Protocol Buffers. You can imagine a public API that is introspected and can tell the client about deprecation and all that.

No, think of it like checked exceptions, you only need to handle the effect _at most once_ before it reaches the top (it's up to you to let it keep getting passed up or handle it immediately), otherwise the compiler will automatically infer the effect types in the layers between.

Old man yells at cloud.

What these people usually don't get is that computer at the end of the day is just a tool. It is a means to an end not the goal. Having a powerful computer for the sake of having a computer doesn't accomplish any meaningful.

"Why did all major software companies settle on parallel career tracks? To keep engineering managers from developing loyalty to engineers."

I think your tone here implies intent

Everyone has some kind of social event app as one of their first ideas. It never works.