IBM To Publish Java Office Suite 242
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."
Wasn't corel going to do this? (Score:4, Interesting)
Re:Wasn't corel going to do this? (Score:2, Informative)
Re:Wasn't corel going to do this? (Score:5, Informative)
Corel probably jumped the gun a little. The thing ran horribly at the time, because bytecode execution was so slow... and the vm's weren't tremendously mature on most platforms, so it wasn't altogether stable. I have a friend who is still using is, and with modern JIT compilers and higher speed computers it really runs like a dream.
Want my opinion? Java version of Word Perfect runs better on Linux than that Wine-enhanced native Linux version they released ever did.
Wine (Score:3, Interesting)
Re:Wasn't corel going to do this? (Score:3, Funny)
I read an interview with some of the people working on the Wine version of Corels stuff, and they claimed that it had been pushed out far earlier than the development team wanted. Apparently there was an internal service pack, never released, that really brought things up to scratch.
Re:Wasn't corel going to do this? (Score:3, Interesting)
I think one of IBM's main problems here will be ubiquity. Since only a fraction of companies use Domino, that means only a fraction of that will end up using IBM's office suite. Who wants to use an office suite that nobody else uses? That's a really scary vendor lockin situation IMO.
Second, though, wouldn't you think that everyone's already learned in or trained in an existing office suite by the time they are ready to purchase IBM's product? Be it MS Office or one of many already existing alternatives
Corel did it sorta, and it stunk (Score:3, Insightful)
It was slow, and depending on which JAVA VM you used depended on how long it would go before crashing.
It will be remembered as one of the many wasted efforts from the java-craze years.
Re:Wasn't corel going to do this? (Score:3, Interesting)
What dose this mean for the future of desktop software? Follow my logic below and see if you hit the same conclusion.
1. For individuals running Namebrand desktops and Portables MSOffice _looks_ free.
2. For those running none Windows OSs. OpenOffice/StarOffice and maybe kOffice are all that matter.
3. For those who currently have contracts with MS.
Spectacular! (Score:4, Insightful)
100% FREE! (Score:5, Funny)
-
http://fink.sourceforge.net/ [sourceforge.net]
Re:100% FREE! (Score:3, Insightful)
However, just imagine for a moment that you're a company with 1,000+ employees. You probably spend at least $500 per person on MS Office+OS licensing fees per year alone. So... if IBM's product delivers, you could shave $500,000 off that budget. And you're getting WebSphere Portal in the bargain.
Doesn't look so bad.
I don't get the point (Score:3, Insightful)
Re:I don't get the point (Score:5, Insightful)
This seems targeted for the corporate environment.
Re:I don't get the point (Score:2)
Tired Of MS (Score:5, Insightful)
Also, I wonder if they will adopt an existing file format, or if they are just going to go on thier own. I would think that people would like it much better, and would be less hesitant to switch to it, if they didn't have to hassle with thier file formats...
Re:Tired Of MS (Score:4, Insightful)
I'm not so sure about this. If IBM guarantees that it is 100% compatible with MS Office products, I can see this happening, but that's probably not the case. The problem as I see it is that MS Office is the defacto "standard" exchange format for office documents. Even if your whole company changes over to a new suite of office tools, you still have the odious problem of sending and receiving "standard" MS office documents to all the people you do business with.
If you haven't worked in "real" office setting before, trust me on this. I can't count the number of office documents I have to send and receive every single day. Personally, I always try to stick to vanilla text files or HTML instead of word documents, since the extra formatting word allows for is important only occasionally. And, in the past I've done my best to use OpenOffice to work with other office documents, but there's always little glitches that are noticible enough that I'd hesitate to use it on something critical, lest a time-consuming and potentially expensive problem arise. If there were some other standard I could use for spreadsheets and powerpoint slides that I'd be *sure* was going to work on the other guy's computer, I'd be all over it. However, the fact remains that there isn't, and no matter what, people will continue to send me documents in MS format, which I'd better be able to read properly or risk going out of business.
So, in summation, I offer a challenge to IBM: I want to see your entire company (and in particular your services division) dump any copies of MS Office, and stick to using your own office suite for document exchange. If you can pull this off for without any hitches (especially after Office 2003 is being OEM'ed with new computer sales), THEN I'll be convinced it's safe to switch.
Newsflash! No one is losing sleep in Redmond. (Score:5, Insightful)
If anything, it bodes well for Microsoft, because it gives them another solution to point to as a competitor, dispelling claims about MSOffice being a monopoly.
File formats? Compatible with Office? I doubt it. That means this thing is boat anchor. Either that, or it will join those thousands of boxes of the old Lotus Suite gathering dust in cabinets that companies got for buying Notes.
If there was an award for software distributed that never got used, nobody would ever beat IBM.
They should... (Score:3, Insightful)
But they should. Imagine if IBM does what IBM typically does well, which is deliver high-end computing in large-scale environments, with this product for users...
Large companies, school districts, government organizations, anywhere that has had computers longer than Microsoft has been in full force will be able to appreciate this. It's a support thing. If you can have a platform independent system that is centrally installed and highly available, you'll make it in evironment
Re:They should... (Score:3, Interesting)
From then on, they only have to upgrade one product every year instead of 2. For some businesses, buy WebSphere for there network may turn out to be cheaper than 400$/machine with Office.
I guess there aren't many Slashdotters that actually think about the possibilities before the make swe
Here piggy, piggy. And the pig comes 1 year later. (Score:3, Insightful)
From the parent comment: "If there was an award for software distributed that never got used, nobody would ever beat IBM."
Exactly. Remember TopView? It was a way of running multiple programs under DOS. That was the beginning, I guess, of the present software incompetence of IBM. Their failures seem to be a political problem with management.
IBM killed SmartSuite so efficiently! One month they bought it, and the next month it was dead! Awesome!
I remember news reports saying that IBM had lost $1,0
Comment removed (Score:5, Insightful)
Re:Here piggy, piggy. And the pig comes 1 year lat (Score:3, Interesting)
Writing yet another windowing system based on the same concepts as the original is not the answer to the problem, taking the time to optimise the existing code is the answer t
Re:Here piggy, piggy. And the pig comes 1 year lat (Score:2, Insightful)
1. It came out recently. It will get faster.
2. It's faster than swing.
3. It's NOT aweful on OSX.
And once someone writes a plugin for the OS, that's it. Nothing else. Look how many times gtk was ported.. or qt? It's not inherently platform itself, but your code itself is since it (swt) uses a fascade pattern to make all the api's common.
Re:Here piggy, piggy. And the pig comes 1 year lat (Score:4, Insightful)
Actually, yes we are using SWT on a stand-alone application project right now. And no, we haven't had any cross-platform problems with it using the same SWT code for Windows 2000, Mac OS X and Linux (GTK, Red Hat 8) concurrently.
As well I found that Eclipse 2.1 for Mac OS X is just as GUI-sluggish as the rest of the OS X apps, so no big difference there. True, Windows beats it hands down for speed, but that's not SWT's fault - it's Mac OS X's fault.
The Linux GTK version of Eclipse 2.1 performed quite well on my AMD 1.47Ghz -- better than Mac OS X's performance and about 80%-90% as fast as Windows.
SWT was designed to be a "thin" abstraction layer. True, the other platform versions of SWT are a bit behind Windows SWT in terms of features (view dragging in Eclipse comes to mind) and speed but I think they are satisfactory. I'm really looking forward to further SWT developments from IBM.
Re:Here piggy, piggy. And the pig comes 1 year lat (Score:5, Interesting)
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.
Makes sense. (Score:2)
A few of IBM's software successes (Score:5, Insightful)
Well, first off there is no IBM Linux. IBM doesn't have its own Linux distribution.
As to IBM's few software successes, they include:
I'd guess you're just a bitter OS/2 fan. Get over it.
Not so successful, when you examine the issues (Score:2)
IBM bought Lotus Notes and Domino, AFTER they were the most important. People use WebSphere because they want IBM support, I think, rather than because it is good software. ViaVoice is horrible compared to Natually Speaking, or at least was when I tested it.
I should have said that IBM has not been successful with PC software. IBM does okay with its mainframe OSs. IBM does, in effect, have its own distribution of Linux. You and I don't download it because we don't have an IBM mainframe.
Re:Not so successful, when you examine the issues (Score:2)
And Linux on zSeries is just RedHat [redhat.com] (or SuSE or Turbolinux) build using a zSeries-patched kernel and sold and supported by the Linux vendor of your choice.
File Formats (Score:2)
The point is that people will always needs to make files compatible if they want to stand a chance against the monopoly that is M$. They will be able to say "Look their is competition" as in the real world it won't make one bit of difference.
Unless of course we all move to XML
Rus
Re:Newsflash! No one is losing sleep in Redmond. (Score:2)
The target of this seems to be a subset of Microsoft's well-publicized next target: Office applications as a network-delivered, subscription-based, package. Not the home users, who won't buy Websphere in the first place and can't afford to lose compatibility with their company's documents, but the corporations, who are Websphere clients already and also can affor to make the transition to another Office suite.
Microsoft is moving away from retail for var
Re:Newsflash! No one is losing sleep in Redmond. (Score:2)
Uhh, this is *already* built into IE (Score:2, Interesting)
I hear the Mozilla crew has finally been thinking about integrating this kick-ass feature.
Re:Uhh, this is *already* built into IE (Score:3, Insightful)
so basically its NOT server side, which is entirely the point of what IBM has done. but oh yeah, MS never encouraged things like comprehension. so lets see, find Microsoft OS enabled thin client, oh yeah, there are not any. then run some IE active X crap and have a HTML editor, or is it a word proc, you bring up both so im not sure what are you refering to.
you manage to compare "shitty java" with asp. hahahhaha
asp is purely junk to begin with, but if the programmer, actually c
Whoring whoring whoring... (Score:4, Informative)
Re:Uhh, this is *already* built into IE (Score:4, Insightful)
So you are comparing the simple little HTML editor to a full blown office right?.
Nice of them to go Open Source (Score:2, Interesting)
Don't believe me? Search google for "DJ's Java Decompiler"
Re:Nice of them to go Open Source (Score:5, Insightful)
It's possible to prevent java code from being decompiled. This can be done using Obfuscation of the code [arizona.edu] - basically converts the code so that it is more difficult to decompile (but not impossible).
The names of the variables and functions could be changed by such a tool to make it difficult to understand a program - as if it's already not difficult to understand without any comments.
Re:Nice of them to go Open Source (Score:2, Interesting)
If you had the code before obfuscation, and need to fix an issue, are you going to take the final product, decompile and fix the obfuscation? No.
You take the original code, fix it, then obfuscate on the way to the compiler. Fixing an application that has had it's code obfuscated (when you have the original code) is really a non-issue when compared to just fixing th
Re:Nice of them to go Open Source (Score:2)
Decompiling proprietary Java apps is not legal.
Questionable benefit (Score:5, Insightful)
Re:Questionable benefit (Score:2, Interesting)
Re:Questionable benefit (Score:3, Insightful)
It does not need to be attractive to you. IBM does not make it's money selling to mom and pop or the typical consumer. It needs to be attractive to the CIOs. I don't know how good this program is but if it can be deployed across an enterprise and then kept up
Java works. There's still hope for an old vision. (Score:4, Insightful)
I wonder IBM will workin on MS Office filters (Score:3, Interesting)
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.
Re:I wonder IBM will workin on MS Office filters (Score:2)
Yeech. Why go to all that work just to embed a crappy language. Better off embedding ruby or python or something. If compatibilty means dealing with VB then I'd rather do without it.
SWT? (Score:2)
makes for cheap clients (Score:5, Insightful)
Think about all those companies that are paying big bucks for all of those client OS's and Apps. Now they can get, for less than $200, loaded PC's (1.1 GHz PC w/Linux installed, no monitor).
Walmarts $199.98 PC. [walmart.com]
Re:makes for cheap clients (Score:2)
People don't want this type of client.
How about an MS Access alternative? (Score:5, Insightful)
What I'd like to see is something programmed in Java, using an embedded Java RDBMS engine such as McKoi, but also able to be used as a front end to any SQL database -- just like Access. The problem with Acces is, of course, that it only runs on Windows. Wouldn't it be groovy to have a cross-platform, true alternative?
Re:How about an MS Access alternative? (Score:4, Interesting)
Re:How about an MS Access alternative? (Score:3, Informative)
(one of the 3 listed overviews:)
A set of tools, such as a data-aware user forms interface, a reporting system and an application server, which provide a development framework for enterprise information technology professionals to write or customise data-aware applications and deploy them effectively across large or small organisations. The GNUe platform boasts an open architecture and easy maintenance. It gives users a modular system and freedom from being stuck with a single-source vendor.
Re:How about an MS Access alternative? (Score:3, Interesting)
MS Access is supposedly designed for small businesses and for small groups in big companies, but after I worked with a small company who uses MS Access to manage their customer records, I've come to conclude that any database does not belong to a small business. There is no reliable or economical way to manage any database for small (very small) business. The only alt
Thin client (Score:4, Interesting)
Also with J2EE being cross platform it should make it client independant
Rus
Re:Thin client (Score:5, Insightful)
In the early days hardware was insanely expensive. Thus having one machine capable of doing everything was needed (and it was the only machine capable of doing it). It was prohibitive to have a sun sparc 10 on everyones desk when they were new and blazing fast. Hence centralised services.
For a while the costs have not been that much different between the two. There was no really easy way to integrate it all into one point - networks were not fast or reliable enough. I remeber running remote X windows at school and just sitting and waiting on the network to load the app. Now, I have an intensive application running in the background, some network hog (kazaa, actuall application, etc) and still get snappy x-windows. Sure it is not as fast as sitting on my machine - but it is only a matter of "feel" not actual productivity loss. Cut out the background stuff and it is hard to tell the difference. Individual productivity was higher when everyone had thier own stuff - no waiting for services to be available, no waiting on the network, etc. The cost in sysadmins was greatly offset by the productivity gains elsewhere.
At some point we will probably shift again - maybe to something no one has thought of. Both the greatness and the suckitude of working in a fairly young industry that grows/changes as quick as we do. It reminds me of something a teacher once said. In our file processing class we went over reading sequential block devices (tape drives). The teacher said "you never know - you may one day need this". While not on a tape drive, I have needed the sequential raed algorithms a few times and was glad I had it. Some really old stuff is starting to become vogue again.
Re:Thin client (Score:2)
(hah! I didn't even have to mention MS and you -still- knew what I meant!)
Key quote (Score:2)
Well, at least he's honest!
good, bad (Score:5, Insightful)
1. Finally it would be easier to work on WSAD and a word document opened together. Anyone who has worked with these mammoth applications opened together would know what i am talking about. By making individual PCs dummy terminals, this could free up PReciOus processor power
2. Easier to maintain / Upgrade. The guys at the IT should definitely NOT be happy about this one. They will probably get laid off now that it is easier to upgrade due to the centralization.
Bads
1. The only good thing about a monopoly is the standard that it establishes. The article talks says the J2EE suite has
"80 percent of the Office functionality most people use".
There would now be a possibility for a doc file developed in MS Office to look different on these IBM systems. Imagine your resume getting rejected because of that !
2. Centralization could suck with Network breakdown. Switching PCs will not work !
I gave up on MS Office compatibility (Score:4, Interesting)
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 [rdesktop.org] to access a single Windows 2000 machine from our Unix desktops, and we run MS Office and Acrobat on them.
Re:I gave up on MS Office compatibility (Score:2)
My expreiments with terminal server indicate that it still needs help. Dialog boxes disappear, windows scroll at the speed of light, and people just close their terminal server leaving tons of open sessions. Oh yea that and it seems to leak memory like a sieve so that all your applications are noticeably slower in the afternoon then in the morning.
Re:I gave up on MS Office compatibility (Score:2)
We have our share of problems with terminal server. Apparently, it counts currently used licenses in a weird way (perhaps that's related to what you said: sessions are not actually closed).
We don't use it that much; just to fill forms in Word or Acrobat.
Re:I gave up on MS Office compatibility (Score:2)
Never had that experience, and I had been using Remote Windows 2000 (with, as well as without Citrix) for a good long time.
That's simple... There's a configuration option that allows you to automatically log-out users afther the idle-time you set. In addition, there is another option that sets how long after they disconnect that they can reconnect before their applicati
Re:good, bad (Score:2)
Of course, we all know that every version of MS Office produces documents that are compatible with the others...
The balance shifts between client and server (Score:5, Insightful)
As Ethernet bandwidth increases, the argument for putting the power back in the server farm gets stronger. The server farm is in a controlled environment, it's easier to manage. If you assume in a few years many corporates will have gigabit Ethernet to the desk, and simple, cheap thin clients running XPE or Embedded Linux, the IBM approach makes sense. It is also going to be cheaper for developing countries to do this from the start than to put big, expensive, rapidly obsoleting boxes on every desktop.
To a certain extent too, it leverages the Linux strength in the server versus its perceived weakness in the desktop.
Corporate IT should be about delivering the necessary, usable functionality to end users. Geeks often lose sight of that. Microsoft might lose sight of it. But it's IBM core business.
Why bother? (Score:2, Funny)
Server side word processor? WTF? (Score:4, Insightful)
It would definetly be a lot more laggy then a pure-java word processor, thats for sure.
Oracle tried a few years back (Score:2, Informative)
On a separate note, Larry Ellison likes to make lots of predictions - has he ever been right?
80% of 10% is? (Score:3, Interesting)
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.
Re:80% of 10% is 8% of the full monty (Score:2)
Re:80% of 10% is? (Score:2, Insightful)
It's not like we don't have the processing power or ram to handle these things anymore and your not going to be running UT with a word processor in the background anyways.
And why is it that people always think that because there are 90+ features that they have no use for, that everyone else thinks the same. It may be certain that people only use some features but everyone probably doesn't use the exact
IBM are missing the point (Score:2)
With a thin client delivery, you MUST be on the network to work. It just doesn't cut it for the people who move around and aren't always in the office - and
Re:IBM are missing the point (Score:4, Insightful)
However, the great majority of workers are only mobile within site, where wireless networking is going to be continuous. And to do productive work they usually need to get resources off the network...they should not be relying on possibly obsolete versions of docs while mobile.
In terms of data integrity, it could be highly advantageous to many corporates if many workers could not do certain things without being connected to current data feeds.
So, I understand where you are coming from, but no MBA 101 for you.
Not a standard Office suite (Score:3, Informative)
At first I thought "What has a desktop Office suite to do with Java2EE, which is a server side technology?"
In fact the slashdot story text is misleading. In the IBM announcement is used a little bit different term - "spreadsheet and word processing 'applications'", where applications is quoted. It comes from Lotus and Java2EE is involved, so it looks like a collection of collaboration tools. Most probably the documents live on the server and the office "applications" are Java thin clients that can show and edit them.
Really nice application for Java2EE, though. What is not nice is that they have bundled the suite with the WebSphere portal, which is a beast of extreme size, both financially and technically. It may be a nice solution for "IBM only" shops, but to little use to other people.
We can only hope that the software is not tightly coupled with WebSphere, but is generally Java2EE compatible, so it can be used with any J2EE server.
I think we're missing the point (Score:3, Interesting)
change may take place in two ways. The first is as mentioned by some other posters, you would get centralized management of the app and be able to reduce your TCO by not having to install/upgrade on every machine.
the second possible shift is where the real potential is. People don't just buy websphere and drop it in, they customize it to do something for them... so, now that there's going to be an office suite in websphere, companies that make customizations to websphere and have custom apps running on it can count on a standardized, cross application office suite being there that they can wrap their application around.
I think that's where the most potential for this is to truly change things.
Re:The computer is the network... (Score:5, Insightful)
Even with desktop apps, when the network goes down - we're doing nothing.
Re:The computer is the network... (Score:2)
If they can move back the clock they can hurt Microsoft and bring in lots of money for their AIX and as/400 bussiness.
Since pc's are no longer simple machines and are getting exremely complex the old mainframe argument of centrally managed lower TCO is getting some attention. Especially since bussinesses want to cut costs. Support is at 10k a desktop per year and rising ever more thanks to harsher licensing.
However
Re:The computer is the network... (Score:2)
WTF? Care to expand on this one? I've never heard of anyone using or desiring VNC on unix servers or workstations. The mind boggles...
Re:The computer is the network... (Score:5, Insightful)
It has the convenient side effect of putting the Lotus code base to work instead of sitting around doing nothing and if its well received new markets open on the desktop for IBM.
Personally I dislike Websphere but I think this is very clever idea which will go down well in the corporate sphere.
This is new code (Score:2)
Re:The computer is the network... (Score:5, Insightful)
Many business, like manufacturing, are so connected to computers that if the computer network goes down then business grinds to a halt.
I've worked in this type of place. It isn't as tough as you think, considering they only worked 2 shifts, leaving 8 hours for maintenance, etc. It isn't 24x7 but more like 16x5.
The biggest issues were desktop apps having problems. Amazing how much that stuff freezes and crashes when people *insist* on having Outlook, IE, Word, Excel, an SNA client (TN 3270) and possibly a CAD viewer (java applet) and maybe an MS Access database or two running all at once.
Believe it or not, Sun has the right idea. Build the network so that it is so reliable it makes the phone and power companies look like slackers. Then move 90+% of the apps back upstream to a professionally-managed & maintained server.
Re:The computer is the network... (Score:2)
Rus
Uh... no (Score:3, Insightful)
The only way it makes sense is if you can also install a local "server" on your PC and synchronize your documents with the real server when network is up. We have a pr
Re:Uh... no (Score:2)
Re:This is a return to 1980 (Score:5, Interesting)
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.
Re:This is a return to 1980 (Score:2, Informative)
In that case you should sit back, and
Re:This is a return to 1980 (Score:5, Funny)
Well, let's see (Score:2)
Portable devices.
In other words, Absolutly fucking useless idea for an office where you have lots of portable devices.
Good point. However, there are some factors affecting this. First, laptops are a bit of a nasty security issue (I won't even get into wireless Ethernet). Lots of times, it's a *bad* idea to have employees take data home. So if all you're doing with the laptops is moving them to meetings, around the company, etc, because
(a) it lets you concentrate lots of machines wherever yo
Re:Can they make it any slower? (Score:3, Funny)
Re:java? (Score:3, Insightful)
IIRC, the virtual machine debate was the fault of Microsoft for not upholding its end of a bargain.
Good troll.
Re:java? (Score:4, Insightful)
Why did they choose to use java and not the faster and more modern C# ?
Because IBM are heavily into Java (and have VMs for all their platforms)? Because C# and the related
(Microsoft was a victim of sun's harh contracts)
I am sure IBM aren't so stupid they think it's OK to violate a contract, or to sign one they don't intend to honour.
as well as it's lackluster performance
Newsflash: the
Re:java? (Score:2)
Stanley Feinbaum to foes list (Score:2)
Instead of people telling Stanley Feinbaum that he's a troll every time he posts, it's *much* easier to just add him to your foes list. Less effort on your part, fewer trolls for everyone else.
Re:java? (Score:3, Insightful)
And .NET is most certainly restrictive - it's Windows only! And not just on the client side, but the server too, where presumably a lot of the back end work in this IBM office of versioning, collaborative, security, authentication, storage etc. would be happening. J2E
Re:java? (Score:2)
Re:Lotus (Score:2, Interesting)
The company itself is strange, a friend of mine did some consulting for them, they have ganja themed commercials on closed circuit tv.
Re:Applix Anyware did this (Score:2)
And it was piss poor. It made the conventional version of crApplixWare look good. I think one of the best investments Sun ever made was purchasing StarDivision and releasing StarOffice to the world, the investment has probably already paid for itself in crApplix and FrameMaker license cost savings within Sun. I've lost many, many hours of work to crApplix's random segfaults, file corruptions, and lock-ups.
Lotus were working on a similar product at around the same time, u
This is not that (Score:2)
This is completely new J2EE code.
The nature of servers and workstations (Score:3, Interesting)
When workstations became popular, things changed. If you don't use cycles, they're simply wasted. So you might as well suck down most of the cycles on the machine. Efficient software stops becoming worthwhile.
Moving to server
Centralized computing DID take off.. (Score:2)
Centralized is the ONLY way to go in a business. 99% of the computing problems in a business today is directly related to the fact Microsoft has pushed a 'workstation' centric network. We are now living with that viewpoint.
They are by nature, uncontrollable and unstable, and expensive to support. ( though it did make the makers of PC's and PC software a hell of a lot of money )
Re:Centralized computing DID take off.. (Score:2)
Central control and high fixed cost to entry-level computing, available in the old mainframe model did not make these things happen. Sure, there's a cost to maintenance, but trying to control maintenance costs is not what leads to growth.