i dunno. maybe its just me, and maybe i haven't read up enough on the plans, but it seems that the concept behind wave isn't as monolithic as its being made out to be here.
seems like its a big idea, sure, turning conversations into objects, but its not something that precludes writing smaller programs to do specific jobs with respect to the objects. google is working on the outlook-in-scale type application in order to try and fully display the possibilities of the wave concept, but the open system will (seemingly, to me, at least) allow for apps with specific purposes. sleeker apps to do smaller jobs and use the objects to interact.
Well I certainly need to learn more about the protocol itself before I can say anything more intelligent on the topic. If anyone wants to join me, I just found this site, which I wasn't aware of, before:
seems like its a big idea, sure, turning conversations into objects, but its not something that precludes writing smaller programs to do specific jobs with respect to the objects. google is working on the outlook-in-scale type application in order to try and fully display the possibilities of the wave concept, but the open system will (seemingly, to me, at least) allow for apps with specific purposes. sleeker apps to do smaller jobs and use the objects to interact.