Please do me a favor and stop putting “ruby” in your package names. I
know it’s Ruby. No one is going to accidentally think they were
supposed to get a Java library from the RAA. Besides, you’re screwing
up my tab autocomplete.
Please do me a favor and stop putting “ruby” in your package names. I
know it’s Ruby. No one is going to accidentally think they were
supposed to get a Java library from the RAA. Besides, you’re screwing
up my tab autocomplete.
I think that it is a good idea at least for Ruby libraries which are
just bindings to libraries written in other languages. (C and C++ for
example.)
Without the “ruby”-prefix there would be a name collision in that case.
I think perhaps the point being for in the Ruby-centric repositories
for libraries to not be named sqlite-ruby or ruby-sqlite as it is.
Talk about confusing, that example kills me. I don’t think that
anyone would argue with it being named ruby-sqlite or ruby-mysql, etc,
in the Debian repositories?
Alex McHale
···
On Tue, 25 May 2004 03:43:45 +0900, Florian Gross flgr@ccan.de wrote:
Daniel Berger wrote:
Please do me a favor and stop putting “ruby” in your package names. I
know it’s Ruby. No one is going to accidentally think they were
supposed to get a Java library from the RAA. Besides, you’re screwing
up my tab autocomplete.
I think that it is a good idea at least for Ruby libraries which are
just bindings to libraries written in other languages. (C and C++ for
example.)
Without the “ruby”-prefix there would be a name collision in that case.
What about projects that will also appear in Freshmeat? Should each
project have two different names – one for RAA and one for Freshmeat?
Exactly how is this is going to be less confusing?
That said, Matz has expressed a dislike of names that have “Ruby” in
them, or even “R”, if the “R” stands for Ruby.
There’s a group of people who believe that projects should be entirely
non-descriptive. Personally, I’m going to start randomly generating
names for my projects; that’ll make browsing the RAA really fun.
— SER
and what if I need to look for it on google or other search engines?
Knowing a pkg’s name may be useful from time to time, and it ned to be
classified in this cases.
I agree that for libraries that are not bindings to existing one the
ruby prefix/suffix may be omitted but not that great problem anyway
···
il Tue, 25 May 2004 03:49:08 +0900, Alex McHale alexmchale@gmail.com ha scritto::
I think perhaps the point being for in the Ruby-centric repositories
for libraries to not be named sqlite-ruby or ruby-sqlite as it is.
Talk about confusing, that example kills me. I don’t think that
anyone would argue with it being named ruby-sqlite or ruby-mysql, etc,
in the Debian repositories?
What about projects that will also appear in Freshmeat? Should each
project have two different names – one for RAA and one for Freshmeat?
Exactly how is this is going to be less confusing?
That said, Matz has expressed a dislike of names that have “Ruby” in
them, or even “R”, if the “R” stands for Ruby.
There’s a group of people who believe that projects should be entirely
non-descriptive. Personally, I’m going to start randomly generating
names for my projects; that’ll make browsing the RAA really fun.
Wouldn’t it though?
Back in the 80s, there was some kind of “namer” software that would
query you for keywords and adjectives and such; it would then piece
together prefixes and suffixes and fragments and generate random
names such as “OctaMind” for you to consider.
Very amusing idea, and it got good reviews. I wonder how many
commercial products actually got named this way?
Haven’t read that much about Matz’ motivations, but I agree with him,
generally. If you’re writing a quick adapter library that binds to
something in C or C++, then sure, put “Ruby” in the name. But other
than that having “Ruby” in the name sounds a bit like an inferiority
complex: “Our language has all the stuff that your other language has!
See, for your Foobar library, we’ve got a Ruby-Foobar library!”
A language like this should be encouraging us to think of approaches
that are impossible in other languages; our names should follow
accordingly.
What about projects that will also appear in Freshmeat? Should each
project have two different names – one for RAA and one for Freshmeat?
Exactly how is this is going to be less confusing?
That said, Matz has expressed a dislike of names that have “Ruby” in
them, or even “R”, if the “R” stands for Ruby.
There’s a group of people who believe that projects should be entirely
non-descriptive. Personally, I’m going to start randomly generating
names for my projects; that’ll make browsing the RAA really fun.
— SER
Back in the 80s, there was some kind of “namer” software that would
query you for keywords and adjectives and such; it would then piece
together prefixes and suffixes and fragments and generate random
names such as “OctaMind” for you to consider.
Very amusing idea, and it got good reviews. I wonder how many
commercial products actually got named this way?
What about the late '90s names picked by high priced consultants:
Accenture
Agere
Agilent
Aventis
…
There is something to be said for picking a name that has nothing at all
to do with your product (Apple, Monster, Yahoo, Amazon), but generally
if you know what your focus is, you should pick something reflecting
that focus. If you’re hungry, would you rather eat at Bangkok Cafe or
at “Anuva”?
I think in a lot of cases it makes sense to have Ruby in the name of a
package, especially when it is a bridge between two worlds (ruby-mysql,
ruby-gtk, etc.) but when it just does some function, that name might
just be enough: (yaml, htmltokenizer, …) But hey, if your software
might do anything and everything and you don’t want to be pigeonholed…
by all means, go for Agurajamaniro.
Back in the 80s, there was some kind of “namer” software that would
query you for keywords and adjectives and such; it would then piece
together prefixes and suffixes and fragments and generate random
names such as “OctaMind” for you to consider.
Very amusing idea, and it got good reviews. I wonder how many
commercial products actually got named this way?
Ghost Wheel, perhaps. There was a thread a while back… the Japanese
has a few possible translations. I rather like the name, despite it’s
lack of obvious connection to regular expressions.
cheers,
Mark
···
On May 24, 2004, at 4:46 PM, Simon Strandgaard wrote:
At Tue, 25 May 2004 08:59:43 +0900,
Mark Hubbart wrote in [ruby-talk:101275]:
But hey, if your software might do anything and everything and you
don’t want to be pigeonholed… by all means, go for Agurajamaniro.
Onigurama?
I think Oniguruma translates into Monster Driver… not sure though.
Ghost Wheel, perhaps. There was a thread a while back… the Japanese
has a few possible translations. I rather like the name, despite it’s
lack of obvious connection to regular expressions.
Originally the letter (\u9b3c) has meant ghost in China, but
the Japanese word ONI means demon in common.