There are people, who prefer pure C, without OOP's "spooky action from distance". Just like language support for OOP concepts, AOP gives you a higher level of abstraction to solve complex problems.
Compile time around third party code, or just yours? Because I was trying to extract a point of difference where AOP does something you couldn't do otherwise.
AFAIK - PostSharp modifies your code based on annotations you specified on whole assemblies, namespaces or just classes during compilation to do stuff that otherwise would be impossible
Without mortgages, housing would simply stabilize at the rental value. This will be lower than the current price -- but not anywhere close to 90% lower. The price floor would be the cost of new construction -- in other words, all the value in the structure, zero value in the land.
Instead of buying MBSes, investors who wished to have real estate exposure would simply supply capital to REITs that owned the properties directly. Banks would run these REITs for a fee, equivalent to the mortgage origination fee.
The equilibrium condition would not be objectively worse than the current equilibrium. You may have a subjective preference for an ownership society, but Germany does just fine with a rental society.
The problem is that it's socially costly to move from one equilibrium to another. If you go from the German model to the US model, then you hurt the renters. If you go from the US model to the German model, then you hurt the owners. You don't start out with a blank slate, so you cannot just pick an equilibrium.
> No mortgages = Detroit. The end result of this idea is not pretty.
The lack of mortgages did not cause the collapse of Detroit. The causation runs the other way.
The collapse of the auto industry led to the collapse of housing prices in Detroit, which in turn led to the collapse of the mortgage market. Who wants to issue mortgages for houses that are dropping in value?
