IBM To Publish Java Office Suite
prostoalex writes "The Big Blue will bundle J2EE-based word processor, spreadsheet, and presentation graphics applications in its WebSphere portal. What's more interesting is that the package is server-side, with functionality of the application being delivered to the user over the network. Both CRN (linked above) and The Register considered that a major move against MSFT."
Subject speaks of the comment.
http://saveie6.com/
I suspect IBM will want to be able to import MS Office files into their system... perhaps they'll share some code with the OpenOffice gang.
The filters in OpenOffice are pretty good... but there's always going to be room for improvement. (plus, those MS file formats are a moving target...) It would be a nice bonus if IBM would open source their filters, or better yet, use the OpenOffice filters and contribute patches. I have no personal experience with recent Lotus packages, but I'm going to guess that OpenOffice filters are more advanced than the Lotus ones by now anyway.
Personally, I'd like to see some basic VBA compatibility... say what you want about VB, but I find it very handy for little custom functions in Excel -- and no, I don't want to rewrite them just to use oO.
Interesting co-opetition if this did happen. IBM working with a group largely supported by Sun, both trying to take a big bite out of MS.
"First it was dumb terminals then network computers and now this. Its dead give it up."
Do you have ANY idea how useful something like this could be to large environments? Where I work, we have 35,000 computers on the supported list. Two or three different platforms worth, PCs, Macs, and some occasional Linux machines. It would be kick ass if we could deploy one version of one productivity suite across the whole network, especially if we could do it with site based central servers rather than having to work on each and every PC on the fucking network.
If this supports server-side file storage, it's even better, since then we don't have to worry about user data any longer. We'll gladly build fault-tolerant servers if we only have to do it for about a hundred machines, and suddenly we can also roll out upgrades to the products with only a few days' work, not months like we currently have to.
The days of dumb terminals rocked. If one broke, we brought another one out, and swapped. If the server broke, we dropped everything and fixed it. Regardless, the user wasn't without a connection or machine for days at a time like which happens in the Windows world. If Microsoft hadn't managed to con everyone into believing that their dumbass standalone workstation idea was the best, we'd probably be using X-Terms now, and have even better centralization of critical data, rather than every user having to know how to copy their data to the network attached storage (and most of them are not interested in learning).
Just because a computing model is old doesn't mean that it's outdated.
Do not look into laser with remaining eye.
I must say I gave up mostly on the alleged compatibility of open-source software with MS Word. There was always something not right in the presentation. Most of the MS Word stuff that I receive is forms from management and outside partners; those people apparently don't know how to make PDF forms.
We have a solution: we use rdesktop to access a single Windows 2000 machine from our Unix desktops, and we run MS Office and Acrobat on them.
IBM already has a Pure Java database in Cloudscape (www.cloudscape.com). IBM acquired this nifty little toy when they brought Informix in 2001. It is an embedded database that is much more feature rich then McKoi.
I am all for the ASP model, and I really think that something like this has great potential. Esp, if I don't have to fire up Office every time I want to make a change to my .doc documents.
My sketicism is driven by the comment
It's a well known fact, that most people only use something like 10% of Words features. It's also well know that marketers like to exaggerate.
True, IBM has experience killing off retail software, like SmartSuite.
But they also have experience dealing well with server software, like Websphere.
This is not competition for today's bloated Microsoft Office running on your desktop. This is competition for tomorrow's subscription Microsoft Office running on your company's big iron server.
Bloat is a not that much of an issue there (and at the Websphere price scale), and I don't expect it to be that bloated, memory-wise. It's likely to have less graphic candy, wizards, and certainly less "covert OS upgrade components" than MS Office.
GUI support is almost certainly a non-issue too. This is Websphere we're talking about: thin-clients, J2EE, Servlets, EJB and Web Services... that kind of stuff. If IBM chooses Applets for their GUI they should be beaten to a pulp literally, and probably will metaphorically. But that is doubtful, unless SWT is much better than it looks right now.
They'll likely use a big, complex Web interface and just require all users to use IE or Mozilla 18.whatever (probably the later for flexibility's sake), which is certainly less than a requirement to install some other custom client OR an Office suite.
I can already hear the complaints: "What? They force me to install a particular browser instead of a 1GB Office Suite? Oh no!". I'm just speculating, but that sounds to me like the sensible solution.
There's a broad market of options for Web-based interfaces that work quite well if you don't have to deal with compatibility issues, your application logic is not the issue, and you have the resources to debug them properly as an application (as opposed to as 'just a website').
This passes the GUI requirements to the browser support of whatever you're using for GUI: Javascript and DHTML works fine. Or maybe they could go for one of those new fancy XML-based 'web-app GUI' projects that one keeps hearing about in Slashdot. Or they can go the plug-in way.
Whatever they find works best for their Websphere market, which is what matters to them here.
Freedom is the freedom to say 2+2=4, everything else follows...