Google Wave is hitting the proverbial shelf tomorrow and I have never seen people this excited about a intangible product. The hype is warranted and I tend to think that Google Wave may move the web into its next tier.
Current development standards require a developer to learn and keep track of a never-ending list of APIs. These APIs essentially allow creators to build projects that piggy-back on web services that have already been established. It seems that every site and web app has one and in order to build using an API, a developer has to spend the time learning how to create an application that incorporates the API’s specific quirks.
One of the reasons that makes Google Wave so interesting is that Google is creating its own protocol for it called the Google Wave Federation Protocol. This is an open source project in order to get full participation from developers and programmers. What this means to developers is that potentially everyone could get on the same page about how to communicate between web services. Theoretically, it means that all IM clients could pick this up and regardless of if you used AIM, gChat or Facebook Chat, you would be able to communicate with each other (much like how email works).
Pounding IE (internet explorer) into submission is always a plus too.
In order for Google to have Wave work correctly in IE6, it has created a workaround in the form of a plugin called Frame. IE6 is, has always been, and hopefully will cease to be the BIGGEST pain in the ass for web developers. Once the plugin has been installed, Google Frame will render content as it would in the Chrome browser…. and allows for HTML5. That means developers can focus on better interaction instead of conforming to IE6.
IE6′s reign of terror is closing faster now because of Google’s friendly monopolization.