EIOffice 2004 vs. MS Office 2003
ryen writes "Designed to compete against MS Office, EIOffice 2004 is coded in Java therefore able to run on both Windows and Linux. EIOffice 2004 offers features which should get a few users' attention, but does it have enough to have people switching from MS Office? Flexbeta has the review." That's Evermore Integrated Office, if you're wondering.
That's Evermore Integrated Office, if you're wondering.
Heh. Not anymore.
Ack, even I'm getting tired of the "we slashdotted your site" jokes.
"Written in Java so it can run on both Windows and Linux"
hehe, what about all the other platforms there's a JVM for? Like, uh, OS X? Solaris?
How myopic.
While I can try out a million different versions of office, and get equal satisfaction. Everything really comes down to standards.
.doc .xls .ppt standards. M$ is still winning the same game, just different players.
Until there is something 10x more superior than
1) Great another competitor, we should support it
2) Its in Java it will suck
3) Java sucks
4) It should be in Perl
5) It should be in C
6) I use vi and troff.
An Eye for an Eye will make the whole world blind - Gandhi
But the web site doesn't have any trial versions.
Its hard to put down $150 without seeing if it will actually open up my spreadsheet and documents.
The review had an eval copy, but no such animal on the web site. Too bad; Do you have to wait for a warez copy to figure out if its worth buying? Makes me think they have something to hide.
Believe it or not, I think real Excel compatibility is the hardest to achieve because there are so many different macros (VB Script), charting features, and other goodies in Excel that its easy to get "locked in".
This is great ! I have been waiting for the helpfulness of clippy combined with the performance of java.
In Canada EI stands for Employment Insurance, something you collect when you lost your job, affectionately known as "The Pogy." So looking at EIOffice, does it mean that your employment in an office is ensured, or is it the Pogy Office where you pick up your cheque?
Please, to all non-MS developers out there: stop chasing Microsoft!
... well, the instant something doesn't work, or just doesn't work exactly the way they're expecting, they'll dismiss your product as a cheap knockoff.
I understand the motivation behind designing office suites to look like Office clones, window managers to look like Windows clones, etc.: the idea is that people switching from MS products will find it easier to get used to the new software if it looks like what they're used to. But I really think this is a fundamentally flawed line of reasoning, for two reasons.
1. No one will ever be as good at being Microsoft as Microsoft is. You may expend endless blood, toil, tears, and sweat trying to clone $MS_PRODUCT down to the last widget, but you'll never get it exactly right. And if you try to lull users into feeling like they're using $MS_PRODUCT
2. Microsoft interfaces may be the "standard," but they're not the best. In almost every market niche I can think of, there's some product that's faster, more powerful, and/or easier to use than whatever Microsoft is pushing. If you're going to copy something, copy something better than Windows, Office, IE, ad nauseam -- or better yet, start with the best as a baseline and innovate from there.
The correlation between ignorance of statistics and using "correlation is not causation" as an argument is close to 1.
El Office - A product of Mexico
'mmmmmmmmm.... forbidden donut'
IIRC, Lotus Development Corp v Paperback Software Intl demonstrated us in 1990 that copying the look and feel in exact form is copyright infringement.
And if you use C/C++ your application will be easy to make fast, no matter what you're doing.
This is a very silly claim, at least as bad as the one you were responding to, that if an application is written in C/C++ it will be easy to make fast.
Then why do we have so many very-poorly-performing native applications out there.
I have seen enough cases where a well-designed Java app outperforms by an order of magnitude a poorly-designed C++ app.
I am all for using C/C++ where it is appropriate, but C/C++ is no magic silver bullet when it comes to performance any more than Java is. In either language, if you have carefully-constructed libraries, porting can be quite straitforward and if you have a design that plays to the strengths of the platform, performance can be reasonable. Performance and portability are always a matter of design. It does not just happen as a result of choice of platform.
When are people going to learn that consumers don't care what language a program is written in? For some reason, the Evermore Software folks are attempting to use this as a marketing bullet point (it's the first point on their web page, even), when Joe User really just wants to know why it's better than MS Office.
I write Java to pay the bills, and as such I'm a big supporter of the platform. But users just don't care. In fact because of the Microsoft FUD machine, saying it's Java might even be a turn-off to quasi-technical people. I once had a government purchasing manager say "Java? We're moving away from that because Microsoft no longer supports it." Idiotic yes, but to paraphrase Forrest Gump: Customer is as Customer does.
Writing Java apps is key for the software developer, because your market suddenly is no longer linked to the hardware platform your customers have. You can sell it to anybody. But from the customer standpoint it simply doesn't matter.