jtd wrote:

On Saturday 15 September 2007 19:12, Rony wrote:

...

JTD wrote:- (Parts without quotes)

...

OO is not ready for use IS an attitude problem. Especially when it is contrary to my (and hughe number of other people's) experience in using both Msorifice and OO

...

(RB) If that was the case it would sell like hot cakes. Retail vendors are always looking out for equivalent solutions.

You have just taken a giant leap into wrong logic. Selling like hotcakes has got absolutely nothing to do with the issues being discussed. Big sales != good software.

Software is created for users, not vice versa. Good software not only means good from inside but an easy to use and intuitive interface outside. For new users it is necessary to train them even on doze software but when pro tools are created as libre replacements to commercial closed software, then they could follow those interfaces so as to eliminate any extra training required for the pro users.

That means it becomes slightly less crappy, usually by increasing RAM (memory leaks), higher speed cpu (limiting cpu load), adding AV (poor security and additional load on cpu). Resources which cost and are better utilised elsewhere.

No hardware upgrades. BTW even linux needs more resources as distros get newer.

...

...

(RB) This is rubbish. If M$ Office and XP crash 10 times a day, most offices will shut down. There will be chaos. Lets not get biased so much that we exaggerate.

I suppose u havent been to a large scale M$ shop with admins reinstalling tens of machines daily. Besides the fairly common shutting down of services for "maintanence". Afair the UK pension system shutdown solid for more than a week. And recently all Vista machines refused to boot in some town in Sweden. There was a case of a banks ATMs (300 of em) infected by some crappy worm inspite of all the "security".

As I had mentioned earlier, Linux is the best option for big organizations. Free of cost license, customisation and high security.

...

(RB) GUI is just an extension of a script. The script you mentioned can be run by simply clicking a gui shortcut to it. It is all about environment. If you have to work in a terminal only environment, naturally command line and scripts is the way. If you are in a gui Instead, there is a gui firmware interface which only the service personnel would understand and they correctly enter the values according to the customer's environment and the gui internally creates relevant scripts and runs them.

Nothing wrong in that except when you have to click ten buttons a 30 times thrice a month, or when the idiot service engineer from the isp presses the reset button on the modem and u having to send your engineer to set things right.

You can backup the config file available in the gui and restore it after any mess ups.