Slashdot Mirror


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.

22 of 478 comments (clear)

  1. Slashdotted by Anonymous Coward · · Score: 5, Funny

    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.

    1. Re:Slashdotted by NoData · · Score: 5, Funny

      There was a server on a farm...

      E-I E-I EIOffice.

      And that server got slashdotted.

      E-I E-I EIOffice.

      With a packet dropped here...and a packet dropped there...

      (why? why hurt?)

    2. Re:Slashdotted by stealthyburrito · · Score: 5, Funny

      At first I thought it was a Spanish version of Office:

      El Office Grando.

  2. Both Platforms? WOW! by the+MaD+HuNGaRIaN · · Score: 5, Interesting

    "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.

    1. Re:Both Platforms? WOW! by Kenja · · Score: 5, Funny
      "hehe, what about all the other platforms there's a JVM for? Like, uh, OS X? Solaris?"

      You're forgeting the Java moto. "Write once, run once, mabey twice, three times if your lucky".

      --

      "Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
    2. Re:Both Platforms? WOW! by Wavicle · · Score: 5, Informative

      I know I shouldn't feed the trolls, but...

      well, you see, Java really isn't that portable.

      I have worked since 1998 on Java software with a focus on UI and portability. Although OS X has never been on my radar, I have worked extensively on other people's code when it was "working fine in windows" but partially or completely broken in Solaris (later Linux as servers migrating over).

      All the compatibility problems broke down to one of three problems:

      1) Solaris patching. I don't know if Sun has fixed this, but patching of Solaris and patching of Java to work on Solaris was a true nightmare. The Solaris JVM was awful (was, I haven't touched it since 1.3 so I like to think it is all better now).

      2) Hardcoding of directory separator characters instead of using File.separatorChar

      3) Fonts. The UI issues on the Unix variants for early Java were huge. Swing didn't hardly fix anything because the underlying problem was truly hideous fonts. To the best of my knowledge, 1.4 has completely fixed this problem.

      To the best of my knowledge #1 and #3 are fixed now. #2 is something you usually only see from recent grads or people new to Java programming.

      I can't remember the last time anything I wrote in Java and packaged as a jar had trouble working in Windows or Linux. Certainly has not happened since 1.4 came out.

      I've worked recently with C/C++ code and experienced C/C++ portability fun between platforms. The code was used for reading a writing DNA chromatogram format files. Worked perfectly in Solaris. Wrote out 4 gigabyte blank files in Linux in the odd circumstance when it would actually run at all. The problem turned out to be endian handling. This problem doesn't occur in Java, however in C/C++ when you simply tell the machine to write out blocks of memory (that happen to be data structures) the resulting byte order is whatever the machine natively uses. The IO routines don't know if one piece is a double, another a long and yet another a short.

      Java is really portable. It's also quite fast. Nearly all complaints about Java's speed these days come from Swing, which is really caused by an overdesign of Swing (from a design stand point, Swing is very, very nice. Unfortunately what makes it nice also makes it quite slow)

      --
      Education is a better safeguard of liberty than a standing army.
      Edward Everett (1794 - 1865)
    3. Re:Both Platforms? WOW! by mrtrumbe · · Score: 5, Interesting
      I respect your opinion, but wholeheartedly disagree.

      So long as you stay away from any native calls, Java code is VERY portable across JVMs (including across systems). GUIs do tend to have some problems, but I tend to avoid pure Java GUIs anyway, due to latency issues (which tend to rear their ugly heads more often in live trading scenarios). If I plan sufficiently, keeping my core infrastructure/business logic in pure Java, using JNI sparingly, and write all of my GUIs in QT/GTK, I have no problems with porting.

      So why bother with Java at all? (I can picture you asking the question, so I may as well answer it.) Simple: I find it soooooo much easier to write good code in Java than C/C++. While I've heard some denounce Java's framework classes as a messy C++ superset, I disagree. It's easy to use, well documented (java.sun.com/j2se/1.4.2/docs/api/ may be all you ever need) and easy to refactor. Combine that with a kick-ass tool like IDEA (www.intellij.com) and you have my personal dream environment for development.

      From my POV, so long as you keep GUI issues out of the equation, Java is as close to the perfect development environment I'm likely to get. I work in a setting where I can keep my business logic and infrastructure pretty well removed from the GUI level. This makes things easy for me. YMMV.

      Taft

    4. Re:Both Platforms? WOW! by dasmegabyte · · Score: 5, Insightful

      WTF are you talking about?

      The sufficiently complex applications *I* have written in Java -- including a mass mail server and a database migration utility -- have worked just FINE on every arbitrary Java installation I've seen. I wrote them on a PC, moved them to a Sun server , and still run them on my Mac. The trick is to write them in pure Java...no native libraries, and when you need a file separator, get it from Preferences...don't assume / (or \, or : for that matter)!

      Now, the difference between Java and GLIB/GDK/GTK is that you only need ONE binary. That's one less thing to worry about supporting...one less thing to have to TEST everywhere. Furthermore, I've rarely seen a Java UI crash unexpectedly. GTK crashes all the time on "beta" systems...like Windows.

      --
      Hey freaks: now you're ju
    5. Re:Both Platforms? WOW! by JUSTONEMORELATTE · · Score: 5, Funny
      "hehe, what about all the other platforms there's a JVM for? Like, uh, OS X? Solaris?"

      You're forgeting the Java moto. "Write once, run once, mabey twice, three times if your lucky".
      Back in 99, Symantec (of Visual Cafe fame) sent me a flyer for a new Java Debugger. They were trying to play off of Java's motto, but "Write once, Debug everywhere" made me laugh really hard.

      --
  3. It's about Standards by superpulpsicle · · Score: 5, Insightful

    While I can try out a million different versions of office, and get equal satisfaction. Everything really comes down to standards.

    Until there is something 10x more superior than .doc .xls .ppt standards. M$ is still winning the same game, just different players.

    1. Re:It's about Standards by DaHat · · Score: 5, Insightful

      Regardless of how superior a new format may be, the fact that many use MS software means that many will stick with MS formats because they are nearly ubiquitous.

      I know I'm going to get flamed for this, however...

      Ex: Many claim Ogg is a superior format to AAC, MP3, WMA and others, however the fact that it is not supported by as many pieces of software and hardware limit its use. The reason that MP3, a format which many claim is inferior to nearly everything continues to thrive is because an MP3 works nearly everywhere, just as a .doc.

  4. Summary of Slashdot comments by MosesJones · · Score: 5, Insightful


    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
  5. It looks interesting by Anonymous Coward · · Score: 5, Interesting

    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".

    1. Re:It looks interesting by cyfer2000 · · Score: 5, Informative
      download

      A chinese page, click the links in the table.

      you won't believe it is a Java software.

      --
      There is a spark in every single flame bait point.
  6. get this out of the way by Tsiangkun · · Score: 5, Funny

    This is great ! I have been waiting for the helpfulness of clippy combined with the performance of java.

  7. Bad Name by greyhoundofdeath · · Score: 5, Funny

    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?

  8. It's becoming a cliche, but ... by Daniel+Dvorkin · · Score: 5, Insightful

    Please, to all non-MS developers out there: stop chasing Microsoft!

    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 ... 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.

    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.
    1. Re:It's becoming a cliche, but ... by js3 · · Score: 5, Interesting

      I disagree. To effectively overtake a product with a commanding lead in the market you practically have to make a clone of it and sell it cheaper. Anything different is too different for many people and they won't switch.

      Many times people just want something better not different. I want a better government not a different one and so on and so forth.

      --
      did you forget to take your meds?
  9. El Office by CitznFish · · Score: 5, Funny

    El Office - A product of Mexico

    --
    'mmmmmmmmm.... forbidden donut'
  10. Interface is copyrightable? by at2000 · · Score: 5, Interesting

    IIRC, Lotus Development Corp v Paperback Software Intl demonstrated us in 1990 that copying the look and feel in exact form is copyright infringement.

  11. Easy to make C/C++ application fast? WOW! by expro · · Score: 5, Insightful

    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.

  12. Language Indifference by MidKnight · · Score: 5, Interesting
    Designed to compete against MS Office, EIOffice 2004 is coded in Java...

    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.