Re: Crippled Products and the IE Question

["Michael Tregaskis" <waderad@i.net.au>]

>Tod; Actually, it's a good idea and practiced rather widely.  Why?  Because
>you make a module take a certain input, expecting it to give you a certain
>result.  This way it can be called by multiple apps without having to
>re-invent the wheel each time you need a similar function.  It's like
>taking OOP to another level beyond where it currently is...
>
>Scott K. McGrath
>mcgrats@ix.netcom.com

Yes, using other modules and dll's and whatever rather than re-writing them
is a good and non-wasteful way to go, but only for programs relying on the
operating system.  When the operating system starts relying on programs...!
Microsoft should offer a patch or update to Win95 that integrates all the
code supposedly needed to run the OS into the OS.

Imagine what would happen if things continue to go this way?  "Yeah, I
uninstalled that stupid tamagotchi game the other day and then I couldn't
open any windows 'cause my OS was relying on window-opening code in the
tamagotchi game".

Also, while I'm here, I might just add something to do with this
inseperable IE/OS thing that's going on.  On my grandparent's Pentium II
266mhz running Win95 (can't wait for Rhapsody!) I got so sick of PC user
cd's using Internet Exploiter that I just went in and deleted the
"Microsoft Internet Explorer" directory.  No problems, nothing went wrong.
All those dreadful dll's and badly coded files deleted, gone, destroyed.
Continued using the computer for hours, not even a cough.  Restarted and
the computer's never been better.  Everything to do with the web just zips
along, Java finally works (IE prevented Java from even loading!!!!) and
Netscape Communicator 4.04 hardly ever crashes or messes up anymore.  So
what's this about deleting IE messing things up?  For me, it was the best
thing I've ever done to the computer!  Microshaft just keep coming out with
more ---- than you'd find in a sewerage farm.

Wade Tregaskis (waderad@i.net.au)