Date: Tue, 20 Nov 2001 11:19:01 +0100 From: "Anthony Atkielski" <anthony@atkielski.com> To: <RoKlein@roklein.de>, "Chip" <chip@wiegand.org> Cc: <questions@freebsd.org> Subject: Re: home pc use Message-ID: <00cd01c171ac$ca0fa0e0$0a00000a@atkielski.com> References: <3BF9B12B.3D521A4D@nycap.rr.com> <20011119220243.A268@prayforwind.com> <009a01c171a9$4eedbee0$0a00000a@atkielski.com> <E1667rO-0002md-00@mrvdom03.schlund.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert writes: > Perhaps this was due to your buggy VIA > Southbridge, mentioned in another > thread, IIRC? That same "buggy" hardware runs Windows flawlessly. > Though KDE crashing possibly indicates a faulty > memory module / memory timing problems... The most likely cause is poorly written code. > As a side note, running a graphical user interface > doesn't automagically mean, you have to use KDE. > There's fvwm, icewm, twm ;), etc... They all have the same drawback. Indeed, even under Windows, the vast majority of problems are related to the GUI environment, not the kernel OS (at least with a stable kernel, such as NT/2000/XP). I think that many people believe that, by just adopting the right OS, you can get a simple, Windows-like GUI. Unfortunately, that's not true ... _any_ GUI with the complexity and flexibility of a Windows environment will be just as complex itself, and just as potentially unstable. And the problem with freeware GUIs for UNIX systems is that the authors simply don't have the resources to beat them into complete stability with exhaustive testing and very careful coding. Typically only commercial developers, who have the luxury of being able to work full-time on a project, are able to do that, and even they usually don't bother to follow through, although they get further than people who are working as volunteers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00cd01c171ac$ca0fa0e0$0a00000a>