Vanguard said:
The idea of shared libraries of functions is quite older than dlls. In
Linux land they're called shared objects and ususally have a '.so'
extension. That's a convention as Linux following the Unix model does
not need an extension to tell it what a file is or does. Yes, there is
some duplication of functionality in Linux shared objects, but for the
most part it is handled much better than in windows land. Much of that
is due to a clearer understanding of what belongs to the OS and what
needs to be handled by the individual application. Another mistake that
MS has made is in not understanding that the interface is not the OS.
Another mistake MS has made is in designing so many features into 'IE'
that make it too easy to hack an enduser's machine. If I can write an
ASP page that can cause your PC to execute code at the system level
just by visiting that page, you as an enduser have a serious problem.
Oh, I don't do ASP anymore. Strictly PHP, Perl and C/C++, thanks. And
very happy to do it.
Some of that came from the lawsuits that forced the OS and application
divisions to be forced into independent development (i.e., anti-trust suits
forced one division to be ignorant of what another did). Just because it
says Microsoft doesn't mean one product knows about another (although there
would still be better communications within Microsoft than, say, between two
independent 3rd parties).
I'm afraid you're being overly optimistic, there. MS holds the
government and any laws that get in its way in complete contempt. Read
the transcript of BG's testimony when he was deposed in the most recent
monopoly farce. He doesn't know who his senior VP's are and he doesn't
know what they do? Give me a break. Go back and look at the provisions
of the 1995 consent decree and count the number of ways they've
violated that. Microsoft does not abide by the law. It is a law unto
itself.
Later,
Andy C.(never #)