Well, I highly agree with your first paragraph as OOo is not the end of the development, but the right way to head. I also think, that more and more office work will be done online. At least as soon as we can online catch up with the desktop apps. Or at least provide the right components the people really need. All the previous movements in this direction sucked completely and never got much attention.

What I highly disagree with is the Java paragraph. Sorry, but the way OOo is integrating Java sucks completely. And I say this as a Java user and advocate. The move was useless, cause I can't see much market for OOo Base and secondly it requires OOo to utilize Java in some weird locations - Wizards!!

And will we really get a reuseable framework? Or even components to use on the web? And how do you want to reuse it in Mono? IKVM? Ever tried it? Sorry, I don't see here much possibility for reuse that is capable to attract users and customers. The backend stuff can be used nicely on the server part.

Well, as I lead a team developing a WYSIWYG layout system for print papers, I can tell you, that writing such a thing is not easy in Java and a lot of boulders are thrown at you from Java, too. Such a tool has to be snappy, responsive, fullfeatured and so on and so on.

I personally don't believe, that it is a good idea to develop anything inside OOo in Java. Start thinking about the stuff after OOo. Integrating Java code inside existing C++ apps can be/is PITA. The currently visible results (OOo Base) prove that. And GCJ? OOo is running much slower on Linux using GCJ/GIJ compared to Suns JDK.