Date: Sat, 8 Jul 1995 08:36:45 -0500 (CDT) From: Mike Pritchard <mpp@legarto.minn.net> To: jhs@vector.eikon.e-technik.tu-muenchen.de (Julian Stacey) Cc: dufault@hda.com, hackers@freebsd.org Subject: Re: Proposal to change name of this list to a less embarrassing one Message-ID: <199507081336.IAA05416@mpp.minn.net> In-Reply-To: <199507060852.KAA02604@vector.eikon.e-technik.tu-muenchen.de> from "Julian Stacey" at Jul 6, 95 10:52:03 am
next in thread | previous in thread | raw e-mail | index | archive | help
> - there's a Hackers Handbook, > `Hacker' is an un-necessary liability to our fine Op System. > > I guess people in the business of providing Unix like OSs to students & > motivated individuals don't encounter much resistance, but I'm trying to > venture into new markets, where the people are less `op. system literate'; > here the word `Hacker' is a superfluous danger signal. I don't really care what the group is called, but I thought I would pass on something I just saw recently in comp.lang.c. Some guy in there was ranting about how "hackers" produce bad code, and went on to list various C constructs that hackers use that are bad. He had some good examples of bad programming practices, but I would simply say that the person using them was a poor programmer, not a "hacker". The Hackers Handbook is a good example of something some of the less technical types may see/hear about and cause them to have a less than a warm fuzzy feeling about the operating system. I always try to point out the correct word to people when they misuse "hacker" to describe people breaking into systems. Get it right and call them a criminal. -- Mike Pritchard mpp@legarto.minn.net "Go that way. Really fast. If something gets in your way, turn"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199507081336.IAA05416>