Chad Smith wrote:
Another thing you have to realize is that no one here has said that
the MS Office model is crap. Based on my understanding of the apps
(that they have little to share), it seems just fine to me.
Personally I prefer OOo but that's because OOo gives me some things
(vector graphics, cross platform, etc) that are important to me.
Don't make me laugh! People call MSO crap every day! *Especially* on
this project's mailing lists.
Sigh... Saying that MSO is crap is not the same thing as saying that
their model (having the apps distinct) is crap. Big difference.
No I am not a developer, but Yes I do follow what you're trying to say
here. It is always your MO to attack my understanding when I disagree
with you. It's really, REALLY, *R E A L L Y* old, and it only shows
your lack of a real argument. One does not need to be a mechanic to
know that a 2006 Viper runs better than a 1969 Rabbit. One does not
need to be a doctor to follow a discussion on how exercise improves
health. Please do not insult me by insinuating that since I haven't
written a computer program that I am incapable of understanding the
basics of monolithic versus modular design. It's very simple. One
big program to do everything (like OOo) versus a lot of smaller
programs that have limited abilities (like MSO).
And yet, you can't grasp the concept that code reuse is a good design
and that code reuse does not go hand in hand with monolithic design. A
Linux system has tons of code reuse through libraries for example, and
that goes hand in hand with it's modular design. You also seem to act
like OOo is just 8 million lines of code in a flat file. Truth is, there
is a lot of modularity in OOo. There is a component model called UNO.
OOo is divided into components (and I don't mean "Writer", I'm talking
about actual functions like "draw a circle") and they have interfaces
and you only manage them through their interfaces. So, just saying
"monolithic is bad, therefore OOo is bad" is overly simplistic.
2) Who called it "elegant"?
Ian has, many times. Most recently, in the email I replied to.
I can't find it.
Question: How much space does MS Office take? I was sure it was a
heck of a lot more than 150 MB. I've heard it's close to 500 MB.
Wouldn't this be an example of how sharing code can reduce the total
amount of code?
Less than 150 MB. I'm not on my home computer, but I've looked at it
before - and it was less the last time I looked
I'd like someone to double check this.
All of that on a Mac, so you can't possibly claim the hidden so-called
"Office hooks" that MS allegedly puts in Windows. (That claim is
bunk, btw.)
How do you know they are bunk? The fact that MS made a version of Office
for Mac does not preclude the existence of hooks in the Windows version.
From what I've heard, they're essentially different programs and the Mac
version of MS Office internally uses filters to be able to read/write
.doc files because those files are essentially a memory dump from Windows.
Like Obi-Wan said "only a Sith speaks in absolutes..." ;-)
I wasn't aware that George Lucas's fictional characters had anything
to do with elegant design of computer programs.
Hey, it was funny. Relax.
Funny, you're the one who quoted a movie character's one sentence
catch phrase to attempt to belittle my point.
Quoting Obi-Wan was meant to be humorous. You really need to relax. You
get your feathers ruffled too easily.
"Beware... fear, anger, hate... the dark side are they" - Yoda
Cheers,
Daniel.
