Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| From | kludge@panix.com (Scott Dorsey) |
|---|---|
| Newsgroups | comp.misc |
| Subject | Re: Linux archeology: KDE 0.1 |
| Date | 2019-04-04 19:03 -0400 |
| Organization | Former users of Netcom shell (1989-2000) |
| Message-ID | <q862fi$f6s$1@panix2.panix.com> (permalink) |
| References | <f0b0nf-e25.ln1@rasp.therandymon.com> <87ftqxvjnr.fsf@violet.siamics.net> <q85e5l$rm5$2@dont-email.me> <ggnagaFt1fU1@mid.individual.net> |
In article <ggnagaFt1fU1@mid.individual.net>, Huge <usenet@huge.org.uk> wrote: >On 2019-04-04, Rich <rich@example.invalid> wrote: >> Ivan Shmakov <ivan@siamics.net> wrote: >>> Neither do I have any better understanding of what a "desktop >>> environment" is supposed to mean and why I may need one >>> nowadays. >> >> A "desktop environment" is a crutch for the windoze users to allow them >> to be able to use a computer without having to learn much of anything >> in the process. > >Pompous twat. Welcome to my killfile. Well, he didn't say that in the most polite way, but on the whole it's kind of accurate. Graphical file browsers are one of the great evils of the modern world. Part of the problem is that they make anything other than trivial operations very difficult, and part of the problem is that they are forced to bind the same click action to completely different operations. Click on one file and it opens an editor. Click on another and it executes. This becomes a severe security issue when people get files that aren't obviously what they think they are. I appreciate the urge to simplify the UI, but you can simplify it way too much, and people have. --scott -- "C'est un Nagra. C'est suisse, et tres, tres precis."
Back to comp.misc | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Linux archeology: KDE 0.1 RS Wood <rsw@therandymon.com> - 2019-03-28 22:03 -0400
Re: Linux archeology: KDE 0.1 Oregonian Haruspex <no_email@invalid.invalid> - 2019-03-29 06:36 +0000
Re: Linux archeology: KDE 0.1 Ivan Shmakov <ivan@siamics.net> - 2019-04-04 16:07 +0000
Re: Linux archeology: KDE 0.1 Rich <rich@example.invalid> - 2019-04-04 17:16 +0000
Re: Linux archeology: KDE 0.1 Huge <Huge@nowhere.much.invalid> - 2019-04-04 21:15 +0000
Re: Linux archeology: KDE 0.1 kludge@panix.com (Scott Dorsey) - 2019-04-04 19:03 -0400
Re: Linux archeology: KDE 0.1 Huge <Huge@nowhere.much.invalid> - 2019-04-05 07:46 +0000
Re: Linux archeology: KDE 0.1 Bob Eager <news0073@eager.cx> - 2019-04-05 07:56 +0000
Re: Linux archeology: KDE 0.1 Huge <Huge@nowhere.much.invalid> - 2019-04-05 16:35 +0000
Re: Linux archeology: KDE 0.1 Mike Spencer <mds@bogus.nodomain.nowhere> - 2019-04-06 02:49 -0300
Re: Linux archeology: KDE 0.1 Huge <Huge@nowhere.much.invalid> - 2019-04-06 09:07 +0000
Re: Linux archeology: KDE 0.1 kludge@panix.com (Scott Dorsey) - 2019-04-06 07:48 -0400
Re: Linux archeology: KDE 0.1 Bob Eager <news0073@eager.cx> - 2019-04-06 11:56 +0000
Re: Linux archeology: KDE 0.1 kludge@panix.com (Scott Dorsey) - 2019-04-06 09:44 -0400
Re: Linux archeology: KDE 0.1 Bob Eager <news0073@eager.cx> - 2019-04-06 13:53 +0000
Re: Linux archeology: KDE 0.1 Rich <rich@example.invalid> - 2019-04-06 13:35 +0000
Re: Linux archeology: KDE 0.1 Rich <rich@example.invalid> - 2019-04-05 13:35 +0000
Re: Linux archeology: KDE 0.1 Bob Eager <news0073@eager.cx> - 2019-04-05 13:38 +0000
Re: Linux archeology: KDE 0.1 Huge <Huge@nowhere.much.invalid> - 2019-04-05 16:36 +0000
Re: Linux archeology: KDE 0.1 Anssi Saari <as@sci.fi> - 2019-04-05 12:25 +0300
Re: Linux archeology: KDE 0.1 Steve555 <Steve555@reallybogus.nodomain.nowhere.invalid> - 2019-06-17 21:39 +0000
Re: Linux archeology: KDE 0.1 not@telling.you.invalid (Computer Nerd Kev) - 2019-06-18 00:22 +0000
Re: Linux archeology: KDE 0.1 Eli the Bearded <*@eli.users.panix.com> - 2019-06-19 06:46 +0000
csiph-web