From owner-freebsd-questions@freebsd.org Sat Apr 16 16:38:09 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E02ABAEE1F1 for ; Sat, 16 Apr 2016 16:38:09 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7E59911ED for ; Sat, 16 Apr 2016 16:38:09 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de (port-92-195-71-243.dynamic.qsc.de [92.195.71.243]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id B8A0C3CC79; Sat, 16 Apr 2016 18:38:00 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id u3GGc0aE003104; Sat, 16 Apr 2016 18:38:00 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Sat, 16 Apr 2016 18:37:59 +0200 From: Polytropon To: "Steve O'Hara-Smith" Cc: freebsd-questions@freebsd.org Subject: Re: Ports upgrade script Message-Id: <20160416183759.a050201a.freebsd@edvax.de> In-Reply-To: <20160416170810.2432e5da717042bb18346ee1@sohara.org> References: <2daca22c-7719-0776-fbe8-3c37021298bf@cloudzeeland.nl> <20160416122425.b603d040.freebsd@edvax.de> <20160416170837.81dddb26.freebsd@edvax.de> <20160416170810.2432e5da717042bb18346ee1@sohara.org> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Apr 2016 16:38:10 -0000 On Sat, 16 Apr 2016 17:08:10 +0100, Steve O'Hara-Smith wrote: > On Sat, 16 Apr 2016 17:08:37 +0200 > Polytropon wrote: > > > Terminology sidenote: The thing is called a directory, not "folder"; > > "folder" is the name of the graphical representation of a directory. :-) > > Introduced in order that people would not be frightened away from a > new user friendly operating system by scary technical terms and instead > have something familiar. Wrong. Earlier representations of the directory (which today is an integral part of a hierarchical file system) was the filing cabinet. This metaphor did not survive. Funnily, the thing we call "folder" is not recognized in Germany as an "Ordner", even though it is typically called that way - the icon rather symbolzes a thing called "Schnellhefter" or "Mappe", but a kind that is not used in Germany. Still, nobody calls them "Hefter" or "Mappe". Look into any field of technology or science: They all have their established terminology, and when you want to do something in that field, you should learn to recognize, understand and use that terminology in order to communicate with others. Because people love car analogies, here's one: "I just got into my metal box, pushed the faster-pusher and rolled to the colorlight at the X. Then I moved the rotator and used the stirring stick. But the liquidpointer was down and I needed a pullcar to get home. The makeheilman said I needed a new puffturnblock and tooth box." You surely understand the intention of this text, but it's really hard to read. Now imagine new car drivers would start talking that way because they "cannot be bothered learning" how things are named. In IT, this is not different. Using the correct and established terminology actually makes the userfriendliness possible. This is no difference if we take words into account or icons. What symbol is used for TV? CRT with bunny-ear antenna. And to save a file? A 3.5" floppy disk. Those objects are not part of the environment those functionalities are being used in, but "from generation to generation" the knowledge of their meaning is taught. And that is why we don't replace words consisting of letters by icons depicting the things we want to communicate about. And because we use a language to communicate, I think it's worth we use the correct words for things. From the point of view of language science, it's important to see the relations of "is a", "looks like a", or "is a symbol for a" as we use the terminology. Of course terminology heavily depends on context. When you talk to mainframers, they say things like "job deck" or "data card", they also say "file" and "dataset". And in the context of this discussion, "directory" probably is the preferred word to be used. > This worked fine until you tried to explain to the > hide bound office worker that it was called a folder because you keep files > in it and they looked over to the wall of files containing folders > containing documents and were puzzled. Files containing other files and directories are usually called archives. Or databases. And why should you put a folder into a folder? This doesn't fit! :-) > Then they found that things moved > the wrong way when you scrolled them and your day just got worse. Don't scroll folders. Scroll the filing cabinet if it has wheels. :-) As I said: It was just a _little_ sidenote about terminology. You don't call your files "dog-eared sheet of paper", you don't call your media files "spool with perforated celluloid", and you don't call your mailserver "bob". You may now continue to see me as a language nutsee. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...