3d3mon
Joined 16 years ago
Joined 16 years ago
Another solution that is more long term oriented and market based: create rival capital-formation pools outside of Wall and Broad, say in the Midwest, South, and West Coast. That way if one pool blows up, we can let them fail and it won't take out the whole economy. It also removes single points of failure from the system. I think the crowdsourcing bill floating in Congress is a great start as it decentralizes capital-raising.
http://www.latimes.com/news/nationworld/world/la-fi-america-...
"The technology behind one patent allows a site to offer suggestions to consumers for items related to what they're currently viewing, or related to online activities of others in the case of social networking sites.
A second, among other things, allow readers of a news story to quickly locate stories related to a particular subject. Two others enable ads, stock quotes, news updates or video images to flash on a computer screen, peripherally to a user's main activity."
http://www.latimes.com/news/local/la-statebudget-fl,0,95571....
To be fair, the CA real estate boom/bust really did a number on the state's coffers. To ignore the impact of the "great recession" is to not see the problem accurately. The govt relied on increasing property tax revenue that disappeared as quickly as the monopoly money used to pay for it (aka subprime loans) and on state income taxes and sales taxes from workers who quickly lost their real estate bubble jobs. If those workers still had their jobs and homeowners still had their homes, we'd find something else to complain about. Moral of the story is be careful when playing with credit.
Another common complaint with null references is that there is no compile-time type safety that you get with option types. The go team could mitigate this by having the compiler check for possible null references that may not have been caught and emit warnings or refuse to compile.