I've also used both, but more M$ Office than OOo. IME, OOo lacks a lot of the worst annoyances of M$ Office (horrible data source handling, awful mail/merge wizards and, as the reviewer says, awkward handling for headers and footers).
OOo is far from perfect, but M$ Office is the most annoyingly quirky set of apps I've ever had to deal with. I tend to believe that those who prefer M$ Office to OOo are simply more familiar with the M$ peccadilloes than with those of OOo. A case of "the devil you know".
AJAX is stupid. Javascript is a crap language with none of the advantages offered by modern languages like Java and C++. 99% of all AJAX apps are certain to be an unmaintanable mess.
Maintenance is a pain because the code is non-modular and poorly structured. And because there is no support for OO constructs, opportunities for code re-use are scant.
To my way of thinking, AJAX apps are an unmaintainable mess. You have none of the benefits of modern language design (modularity, OO structure) and your presentation layer is horribly intertwined with your program logic. And the same code gets cut and pasted all over the show. Yuck!
I prefer a combination of JavaBeans and JSP on the server side with little or no Javascript. Yes, this still suffers from the page reload problem, but it least it can be maintained. For responsive desktop apps, write 'em in Java (or VB or Delphi or C++, but Java is mostly cross-platform).
JSP still has the problem of mixing logic with presentation, but you can keep that to a minimum by judicious use of JavaBeans.
Oh, and most of the AJAX programmers I know write strictly for IE, which renders the whole discussion fairly moot anyway.
Slashdot Mirror
It'll cause problems for software developers too. Will there be APIs and network features missing from some versions? My brain hurts!
I've also used both, but more M$ Office than OOo. IME, OOo lacks a lot of the worst annoyances of M$ Office (horrible data source handling, awful mail/merge wizards and, as the reviewer says, awkward handling for headers and footers).
OOo is far from perfect, but M$ Office is the most annoyingly quirky set of apps I've ever had to deal with. I tend to believe that those who prefer M$ Office to OOo are simply more familiar with the M$ peccadilloes than with those of OOo. A case of "the devil you know".
AJAX is stupid. Javascript is a crap language with none of the advantages offered by modern languages like Java and C++. 99% of all AJAX apps are certain to be an unmaintanable mess.
And I suppose the kids in the African AIDS orphanages deserve what they get as well? Even though they were born with the disease?
Maintenance is a pain because the code is non-modular and poorly structured. And because there is no support for OO constructs, opportunities for code re-use are scant.
Luke
To my way of thinking, AJAX apps are an unmaintainable mess. You have none of the benefits of modern language design (modularity, OO structure) and your presentation layer is horribly intertwined with your program logic. And the same code gets cut and pasted all over the show. Yuck!
I prefer a combination of JavaBeans and JSP on the server side with little or no Javascript. Yes, this still suffers from the page reload problem, but it least it can be maintained. For responsive desktop apps, write 'em in Java (or VB or Delphi or C++, but Java is mostly cross-platform).
JSP still has the problem of mixing logic with presentation, but you can keep that to a minimum by judicious use of JavaBeans.
Oh, and most of the AJAX programmers I know write strictly for IE, which renders the whole discussion fairly moot anyway.
Luke
When I was still using IE, I got hit on a regular basis by various malware infections, and I certainly didn't install any of it.
Thanks God for Firefox.