> 3. Imperative programming is IMHO a natural fit for Web programming. I disagree with this, especially in a RESTful world. It is very convenient, and obvious

> 3. Imperative programming is IMHO a natural fit for Web programming. I disagree with this, especially in a RESTful world. It is very convenient, and obvious, way to look at a web request as a referentially transparent function for the most part. And the non referentially transparent requests really do change the world. We are moving our backend to a bunch fairly clear workflow of, that has layers that look like: Get DB stuff -> referentially transparent -> Write DB stuff And these can be arbitrarily nested. It works pretty well, it's easy to reason about, and it's pretty easy to write.