"Stanislav Malyshev a.k.a Frodo" wrote:
>
> OE>> point to the same actual data). This technology actually seeks
> OE>> out duplicate files and saves space by storing them only
> OE>> once - it's completely transparent (unless you could your
>
> That's a nice try - especially when you expect them not to be one. :)
I'm not sure I understand what you mean, but if you are talking
about the user not knowing that two files actually point to the same
actual data - then the user shouldn't care. If one file is changed
then it would be un-binded and you'll have two seperate files,
so it doesn't really matter.
>
> OE>> transparent - but with MS it usually is, you can never
> OE>> know why NT crashes :), and it's actually a darn good idea.
>
> For Microsoft's package mis-management - sure. When every package brings
> with itself all Microsoft Runtime - it's darn good idea to go behind the
> scenes and bind copies, instead of making descent package management
> system and give vendors ability to know beforehand what is installed on
> the system. Having full control on OS environment, registry, etc. - is it
> *so* hard to do that for 10 years? Darn bright idea - we'll create problem
> and then we'll solve it most preverted way with large fuss about
> "technology advancement".
I have to point out that although MS's package management (or - OK -
mis-management)
has always been lacking, the real problem with their package management has
been their 'philosophy', or maybe the philosophy of people writing
applications
for Win32. After all, everything was supposed to go in one directory
(system/system32)
and not create useless duplicates, but the problem was that when the basic
libs (mfc
for instance) were updated it broke things - and they never bothered to
give
developers the ability to use two different versions of a library w-o
copying
the library into the app's directory, or linking staticly. Doesn't seem all
that different than other environments, although on unices you'd have much
better luck using two different versions of a library on the same machine.
But hey, when RH moved to glibc it broke some things as well.
Now...to sum up, yes, MS do stupid things. Always have, always will. They
lie, cheat, steal, rape - uh, got carried away there, but anybody at
all can have a good idea. However, you got it all wrong when you said
that this comes to solve the mess of duplicates of library files (also,
developers _can_ check if the system already has the library file they
require - even on Win32 - they just don't bother to as that mentality
doesn't exist on those kind of platforms) - it actually came forth
when developing a remote installation system, where you might need to
store tons of slightly different images of the same install.
Also, a package management system is a non-issue if you want to run
this on a file server storing home directories.
Oh, one other thing: MS has a cute package management solution, it
just doesn't work as it should. It's MSI, you might have heard about it.
The idea is basicly OK (making sure no file is removed/replaced if
used by another package, saving copies of a file before replacing it,
allowing a roll-back). The real problem is that after all, it's just
a patch. Unless developers (including Microsoft! They are so large right
now that you can get a brand-new application just released by them
that DOESN'T use MSI, and wouldn't not install because of it :) actually
use it, it's useless. And what about legacy (and by that I mean
applications
which do not use MSI) applications? Again, a patch. Oh, and it doesn't
really let you know what's going on, as opposed to Debian's package
management, or RedHat's. If something goes wrong with an MSI installation
the best you could hope for is something like:
'There is an error' [ok, retry, cancel, die].
This thread was OT to beging with, but I think that
it's always a good thing to see what goes on in the other
side - people should not always assume their way is best
(and especially should not come to a conclusion 2 lines into
a webpage, even if it's a Microsoft webpage).
--
"You will now die. Make whatever rituals are necessary for your species."
- Ur-Quan, Kohr-Ah
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
