From: Eli Zaretskii Newsgroups: comp.os.msdos.djgpp Subject: Re: gdb problem or just silly me - please help Date: Mon, 08 May 2000 20:47:40 +0200 Organization: NetVision Israel Lines: 21 Message-ID: <39170BCC.EA7F2595@is.elta.co.il> References: <0oidhsovvtqs9ga2fnfoqar6vphbpdspo2 AT 4ax DOT com> NNTP-Posting-Host: ras1-p109.rvt.netvision.net.il Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: news.netvision.net.il 957808075 1010 62.0.172.111 (8 May 2000 17:47:55 GMT) X-Complaints-To: abuse AT netvision DOT net DOT il NNTP-Posting-Date: 8 May 2000 17:47:55 GMT X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,ru,hebrew To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Damian Yerrick wrote: > > >The addition of LFN functionality when Windows starts is analogous to > >the additional functionality in, say, keyboard remapping that you get > >on Unix when you start X. I fail to see how does this reveal anything > >(good or bad) about the design. > > That LFN support is tied to having Windows resident in RAM. > That keyboard remapping is tied to having X resident in RAM. LFN is a feature of Windows; keyboard remapping is a feature of X. You cannot have the feature without starting the package that provides it. > Product tying is thought to be bad and to result in bloatware; > hence the *n?x philosophy of "one tool for one job". A package as large and complex as Windows or X cannot be a tool for a single job. If it were, you would need to spend eons to set up all of those one-job tools so they work. You'd need a separate tool for graphics, another one for mouse, yet another for keyboard, one more for fonts, etc., etc. It would be a user's nightmare (not that it isn't already ;-).