I've been wondering over the last couple years during this financial mess, why did we allow those financial institutions to become "too large to fail" in the first place? Aren't there some kind of regulations to prevent that?
Today, I learned a little more about our country's economic history and about the Glass-Steagall Act. Some smart people are recommending setting things back up the way they were when the economy was running smoothly. Sounds pretty reasonable to me. So I decided to write a letter to my Senators and Representative in Congress.
Here's the text of that letter:
Can you please introduce a bill to put the Glass-Steagall Act (Banking Act of 1933) back in place and/or other regulations such as those that served our country so well after the Great Depression? If the deregulation of the ‘80’s and ‘90’s (Depository Institutions Deregulation and Monetary Control Act, Garn-St. Germain Depository Institutions Act of 1982, and Gramm-Leach-Bliley Act) hadn’t repealed provisions of the Glass-Steagall Act, I’m sure we wouldn’t be in the mess we’re in now.
Before the Depression, there was a credit crisis in this country every 10 to 15 years. Then after the Depression when the regulations were put in place, the economy was running smoothly. We didn’t have a problem again until after Congress started removing those regulations.
Another suggestion:
I’m sure we will repeat this financial disaster if we continue to allow institutions to become “too big to fail”. Can we not use the existing anti-trust laws to break up these organizations so that this doesn’t happen again?
If these suggestions are not feasible, please explain why.
Thank you.
I've been hearing a bunch about Google Wave, but didn't really know what it was. I just wanted a simple idea of what it
- Google Wave is a web-based application (like google maps, gmail, etc.).
- It's basically next-generation email (what would email look like if it were invented today).
- You would use Wave instead of your other email client (such as GMail or Outlook) to communicate with people.
- The name came from the show, "Firefly", in which communications are referred to as waves.
- A "wave" is like an email thread -- as people reply, the additional content gets added to the wave.
- You specify which people are on the wave -- sortof how you would specify the recipients of an email.
- If you shut down Google Wave and then later re-open it, you'll see if people have updated any of your waves -- just like you see when something new arrives in your inbox in regular email.
- If you're currently looking at a wave and someone on the wave updates it, you see the updates in real-time (character by character). In this way, it's like IM, but better -- you don't have to wait through the "so and so is typing..." before you get to read it, so it's much faster communication.
- Multiple people can edit the same wave at the same time and see eachother's changes in real-time.
- You can drag and drop images onto a wave -- this requires Google gears, I think.
- You can add content anywhere in the wave -- like replying to a bunch of questions in an email "in-line".
- When someone new is added to the wave, they see the whole thing and can "replay" the evolution of the wave from its beginning to see how it changed over time.
- You can do a kind of sub-wave if you want to keep something private from the whole group that might be on the entire wave.
- Embedding/Blogging: You can embed a wave widget somehow in your blog (or in any site/application, etc.). Then if you add the proper "bloggy" robot user or whatever to the conversation the wave automatically is published to the blog. Comments made to the wave on the blog get updated real-time back in the regular wave client.
- It's open sourced
- There's an API that developers can use to do more stuff with Wave and extend it.
For more, there's an hour and twenty minute video here: http://wave.google.com/help/wave/about.html#video
