On Sunday 21 October 2007 19:39, Rony wrote: > jtd wrote: > > On Thursday 18 October 2007 16:09, Rony wrote: > >> Expressing problems about Linux does not mean > >> you have to attack Windows or its users every time. > > > > Windows is totally crappy as are the service providers who ride > > it's coat tails. > > Pure bias. > > > Even with their pathetic reliability, usability and > > security standards most closed software (eeven under linux) have > > become less secure, more bloated and unmaintainable. Nvidia > > graphic, samsung printer drivers, adobe acrobat reader are cases > > in point. Under M$ the os and it's architecture is one big mess > > that they cant fix it since 1995.The less said about them the > > better. BTW we worked very closely for 3 yrs with dos and > > mwindoze3.0 to 3.11. So i know what i am talking about (though i > > dont remember all the details 15 yrs on). > > Times have changed and windows has come a long way.
Dream on. The underlying stuff is still the same as 95 and even earlier in the case of M$OS and hence the problems remain exactly the same. These are archtectural goofups many directly imposed by HMBG. Recently someone found that calloc hands out dirty pages in vista. MY MY... the more things change the more they are the same - this was one of the worst problems in 3.xxx (WARNING: i havent written a line of code on doze since 98, knowing fully well that whenever they fix the problems, you will have to rewrite everything anyway) > >> If you face > >> problems in Windows, its crappy. If others face problems in > >> Linux, they are the ones wrong. > > > > No. It's when they say "abc on linux is not ready for use" that > > they are wrong. > > It will have to cater to users, not vice versa. You still dont get it (unlikely u ever will). Compare a app on linux with another app on doze ONLY if the underlying protocols and formats are open and unencumbered. If they are not you are making a blatantly wrong comparison. Catering to a user in a hole willfully there is not possible until he gets out of the hole dug by the closed software companies. So stop playing victim and get out of the hole. > >> This is the wrong attitude that triggers flames. > > > > Aha. I hope u get it. > > I hope you get it too. I got it long back and did the wise thing. You still havent and continue to make comparisons and statements based on ZERO understanding. CSS users all the while hide behind the statement that this or that does not work the way it does in doze. I repeat that is because of encumberances or willful violation of standards / good practices by CSS. There are extremely few closed systems that actually have genuine advantages. Eg. Sun solaris ZFS ( but it is encumbered by patents) addresses several problem areas in large file systems. > >> All software whether libre or closed have problems and the > >> approach to solving the problems is no different. > > > > Rubbish. The problems and causes are totally different. The > > approach to solving them could not get more different. FOSS > > relies on public review and contribution. CSS specialises in > > hiding the crap that's all. > > It is the same for both except that the review is done publicly in > FOSS and privately by the company in CSS. In both cases bugs are > reported and updates are made available. Wrong again. There is nothin to review with CSS - there is no code. Dont confuse observing some result with reviewing. U can make a patch if u know howto with foss. Can you with CSS? Also dont confuse sending bug reports to companies with sending bug reports to developers. The company is not the developer or in most cases even the maintaner. We were on a project for an external company who wanted to use a closed toolchain to cut development time. We refused saying that end results were not guranteed. The project went to someone else. Nine months later the project failed cause the toolchain had bugs. The toolchain was developed for a french company's hardware by an Indian subcontractor (who further subcontracted). So u wrote to the french, who wrote to India, who wrote to their subcontractor who would send a new blob. I am sure more time was spent debugging the blobs than reviewing their own code. The situation is infinitely worse for packaged apps. > In both cases there is a > huge community out there ready to help and solve problems. Wrong again. in the case of CSS it's not bug fixes but stupid workarounds offered by the community - the companies may provide a fix in the next release. In the case of foss you dont wait for a next release - just downlaod from cvs and recompile. There are many more important differences, but until u get the basics the rest does not matter. -- Rgds JTD -- http://mm.glug-bom.org/mailman/listinfo/linuxers
