Re: Experience the New Windows

["dodobh@xxxxxxxxxxx" <dodobh@xxxxxxxxxxx>]

Sandip Bhattacharya spewed into the ether:
>I agree partially here - Java SDKs have alwayz given me lot of
>heartbreaks whenever i tried to install it on an remote server. The
>server guys prefer upgrading only the kernel, without upgrading >glibc.

>How much is this different from windows?
>On windows, you are told - "to install this blah-blah, you need
>service-pack blah-blah" or "VCRT-blah-blah". In linux you are told,
>you need glibcv-blah blah, or krbvxxx etc.
Not much of a difference. Just rpm --rebuild *.srpm :)

>OFCOURSE i am talking of installing *binaries* here as RPMS. I would
>NEVER expect a non-techie user to compile tar.gz or SRPMS. Bah! Ever
>seen any windows program that needed compiling before it could be
>used? Just imagine people compiling IIS before using it!
Hmmm, when MS starts shipping devel tools and source as part of the default install, I'll be one of the first to do that :).

>We have to admit that linux still has to bridge the road between
>reliability and user-friendliness. And lets all see to it that it
>reaches there as fast as possible. It has already covered half the
>path - reliability! 
Unix has been designed to be -- An OS of the programmer, by the
programmer, for the programmer. So, given the specific user set that
Unix was originally designed for (and as Linux is a clone, Linux also)
Linux has achieved its goals quite well.
Actually, given that non-programmers can use it quite well, it has exceeded the original specifications of its parent.


>And don't give other folks the line - "If all you could is crib, why
>don't you go ahead and do something about it?". That's like talking
>like the "government" - take it or leave it or (ok my analogy is not
No, its like this:
If you have a problem on windows, you pay someone else to fix the problem, hope that your vendor releases an upgrade which fixes the problem, or you pay big bucks for the tools and roll your own stuff out. And watch out for those nasty EULAs.
On Linux, you have the tools required to fix your probelm available to you. so the third option is much more feasible. I agree, this is not a solution for all problems (too many of those), but some problems n be fixed this way. It is actually possible to contact developers for most Linux products, get some help and get the s/w running.

>it pisses them off real bad. As it is, it's a nightmare for hardened
>windoze folks to shift to linux. Comments like that will make it real
Actually, with KDE and GNOME mimicing the windows interface so much, 
shouldn't be that tough.
The biggest problem is the lack of a decent Office suite.
(Star Office doesn't quite cut it, and Koffice isn't upto the mark just yet)
Similarly with Mozilla, its like its almost there, but not fully.

The biggest problem I have found getting someone to try Linux has always been the impression that Linux is hard to learn.
It contrasts with my impressions of Linux being easy to learn.
Took me about 6 months to learn while doing my college courses, and extra curricular activities and without Internet access.
I was comfortable within the first week though.

>repulsive. Criticism should always be welcome. Be a sport yaar! ;)
Constructive criticism always is.

Devdas Bhagat



------------------------------------------------------------
For Valentine's Day shop by Brand, Product, Price, Store and Location!
http://shop.storerunner.com/shop.asp?pdef=home&trsid=3080