
"the line from Microsoft is that Office Web apps will "complement" Office on the desktop or smart phone, rather than match its functionality."
I can see why. Actually there are (probably) at least 2 reasons. Firstly, MSOffice is a nice lil' earner right now, and if MS wants to keep collecting the provervial golden eggs, they must avoid fucking* the golden egg chicken. Secondly, have you had a look at the size of the frigging MSOffice package recently? By 2010 they will need to ship the thing on BluRays or dedicated hard drives**. And the RAM usage is as horrendous as OpenOffice's, whithout the excuse of the JVM overhead. Even if you're a hardline Moore's law believer, it is hard to imagine that beast running smoothly across a network on a ressource-strapped mobile device (which I suppose should be the main market for networked office apps).
""The primary effort is to make sure rendering translates down to the mobile form factor quite well," Bryant said."
Well, failing that they could always try and make sure that the rendering translates well from a version of MSOffice to the other, or from one app to another in the same version of MSOffice, or even from one machine to another using the same version of the same app***. Pick any. They all badly need to be fixed.
Of course none of these concerns really matters, because in any half-serious circle one already looks like a frigging clown for using MSOffice -bonus points for use of the embedded stick-figure "art". No further harm can possibly done, unless the MBA crowd suddently gets a clue. But if these guys ^h^h^h^h persons were clue-friendly, they wouldn't have got a MBA in the fist place, would they?
Beer icon as I might have had a couple. Not this piss-poor MS lager, either. The real open source bitter deal. OK, stop the hissing, I'm gonna go home now. Would you please call me a cab? "Sure thing. You sir are a cab" WOoosh... missed
PUNCH!
WOOOOOO-sh.... bump!
Taxi? Don't mind the black eye, or the scant clothes. I'll get my coat back tomorrow.
That's all folks...
*or plucking. Or whatever FoxNY says: http://www.theregister.co.uk/2009/09/17/keep_plucking_that_chicken/
**note to the hairtrigered Redmond fans: this is meant as a _slight_ eggs-ageration.
***Actually that's a flaw in most WYSIWYG office applications: as far as rendering is involved, they all fail the machine-to-machine portability test. MSOffice is arguably the worst -with problems between apps on a single system-, but they all do fail. I am not a fan of the whole onscreen-rendering-while-you edit (WYSIWYG) thing, but if you go for it you might as well do it properly. Embedding fonts and display properties would be a good start, and now that everyone seems to be using markup languages it wouldn't even add too much to the final file size (as opposed to when changing the font color for a single character used to double the size of your MSWord document -sometimes, for some reason). The current half-baked "substitution table" solution is worst than the problem. It merely hides the issue and thus prevents you from fixing it. It's especially annoying when you send a document to collaborators for review and it comes back whith 2/3rd of the modifications being "helpful" formatting changes that you have to revert, knowing perfectly well that said collaborators spent most of their time "fixing" the layout instead of focussing on the content. How I long for the return of the glorious days of typesetting software... (LaTeX is kinda out, for reasons obvious to anyone who used this ancient and bloated thing. I much prefer Lout for general purpose combined with jgraph for fast data plotting. http://sourceforge.net/apps/mediawiki/lout/ **** and http://www.cs.utk.edu/~plank/plank/jgraph/jgraph.html ****. But that's just me)
**** if El Reg's line-breaking prevents you from getting there, you're probably not worthy. Too bad. Keep using MSOffice. Do try OpenOffice on your free time, though. You'll like the "integrated suite" experience that MS keeps away from you.