Live data from Hacker News

Why the name?

wiki.debian.org

91–100 of 101 posts

Re: Why the name?

#91
post #7

"python - is of course a Monty Python reference" I had no idea! Makes me love it even more.

And the Python Package Index, https://pypi.python.org/pypi , is also known as the "Cheese Shop".

I never understood why you would name a package index after something that's literally got nothing to show... I know the reasoning, but it still feels strange.

Re: Why the name?

#92
post #7

"python - is of course a Monty Python reference" I had no idea! Makes me love it even more.

One of the ideas I liked most during the inception of Python 3000 a.k.a. python3 has been to rename python3 to blackadder. Another snake, another great british comedy.

Re: Why the name?

#93

Earlier quoted context omitted.

I personally find the man pages very dense and poorly organized. `man grep` for example is my own personal nightmare. I think the man pages should introduce a policy of simple usage examples instead of throwing 99% of information you don't care about at you at once. Something like http://bropages.org/

If you want high quality man pages go look at openBSD base, truly exceptional. Even then, man pages nowadays are massive compared to what they were intended to be, complexity is the bane of all software.

Seconded. When I was starting out in Solaris sysadmin, I'd read the Solaris man pages for local details, but the OpenBSD pages to see what the hell the command actually thought it was doing.

Re: Why the name?

#94
post #14

Earlier quoted context omitted.

Wait till you find out why the IDE that comes with the official Python package is called IDLE ;)

Or read through Python's docs and find the hidden Monty Python references :-)

They are very obvious and not hidden to me.

Re: Why the name?

#95
post #90
post #83

> Giving cryptic names to software is a well-established UNIX tradition God, this is so true! I seriously think that world would be much better already if we would just rename many of well-established binaries and C-functions to more-intuitive, better convention. Even without changing APIs that much (which would be great too, of course).

Good luck with that. We can't even give the creat() system call an 'e' at the end. (Not that it should be used much these days; the 'creat() then open()' idiom is a race condition waiting to happen, so 'open()' has grown the ability to create-and-open in one atomic operation. That seems to handle most of the file creation that Unix programs need to do.)

creat was always create-and-open.

Re: Why the name?

#96
post #86

The etymology of Unix programs: very interesting! The writers of this page also have a sense of humor: > bc > originally a front-end for dc ("desk-calculator"); modern GNU bc is instead a backwards-compatible byte-code interpreter for dc, but what it stands for is still "basic calculator"

While a lot of the names have humorous origins, I don't see the humor in this particular entry at all? Can you explain?

Backwards Compatible

Byte Code

Re: Why the name?

#97
post #86

The etymology of Unix programs: very interesting! The writers of this page also have a sense of humor: > bc > originally a front-end for dc ("desk-calculator"); modern GNU bc is instead a backwards-compatible byte-code interpreter for dc, but what it stands for is still "basic calculator"

While a lot of the names have humorous origins, I don't see the humor in this particular entry at all? Can you explain?

I was amused that they introduce it as a "[b]ackwards-[c]ompatible [b]yte-[c]ode interpreter". Not sure whether that's what the GP meant.

Re: Why the name?

#100

Great fun. One minor nitpick - the story of "Apache Server" being originally derived from "A Patchy Server" is a long-standing myth; the name was originally intended to be a tribute to the Apache Native American peoples. The Wikipedia article on Apache ( http://en.wikipedia.org/wiki/Apache_HTTP_Server ) includes a link to an interview with Brian Behlendorf ( http://www.linux-mag.com/id/472/ ) where he explains how th…

I personally attended a talk presented by Brian Behlendorf at the ISPF (an early ISP conference) in 1999 (which predates the 2000 Linux Magazine article). In his talk, he used the "A Patchy Server" explanation. He made no mention of any other etymology that I recall.

So either Brian was deliberately propagating the myth himself ... or maybe there's some retconning going on.

Post reply on HN