> ps You might be concerned about the name. Well, CPAN has a module
> which matches /fuck/ too. However, if everyone really thinks
> it is a problem, I don't see a problem with s/fuck/funk/g
Well, I'll speak up. I find the name needlessly crude and offensive. I
see no reason to use such a name and would strongly prefer that Parrot
didn't. Parrot is a collective project representing a community of
developers, and I, for one, don't wish to be associated with needlessly
crude and offesnsive language.
--
Andy Dougherty doug...@lafayette.edu
Good for you, I agree (FWIW, since I haven't done much parrot dev - yet),
and it's also unprofessional, which may not matter now but might down the
road. Yes, the language is called that... do we have to (sorry) parrot it?
Dave
Isa. 40:31
The point is well-taken. We need to either rename the directory and
appropriately excise the docs, or move this out of the repository.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
d...@sidhe.org have teddy bears and even
teddy bears get drunk
--Josh
(mmm.. brainspork)
Since this thread has resurfaced, I'll speak up too. And my
not-so-humble opinion is: It's just a word--get over it.
Generally, I try to avoid these words in mixed company, since other
people dislike them, sometimes very strongly. But in this case,
Brainfuck already has an established name. We should use it, even if a
couple people won't understand that it wasn't our idea to call it that.
--Brent Dax <bren...@cpan.org>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
"If you want to propagate an outrageously evil idea, your conclusion
must be brazenly clear, but your proof unintelligible."
--Ayn Rand, explaining how today's philosophies came to be
Tanton
> Andy Dougherty:
> # Well, I'll speak up. I find the name needlessly crude and
> # offensive. I see no reason to use such a name and would
> # strongly prefer that Parrot didn't. Parrot is a collective
> # project representing a community of developers, and I, for
> # one, don't wish to be associated with needlessly crude and
> # offesnsive language.
>
> Since this thread has resurfaced, I'll speak up too. And my
> not-so-humble opinion is: It's just a word--get over it.
Sorry, but try explaining that to my young daughter who was reading over
my shoulder last evening asking "What are you working on, Daddy?"
It's "just a word", yes, but I think it's a needlessly crude and offensive
word. I understand and respect that others disagree.
--
Andy Dougherty doug...@lafayette.edu
There are a lot of words, Brent--that doesn't mean they're all
appropriate in all situations.
It's not our language to rename, though, so either the creator OKs it
or it goes. If there's an acceptable alternative spelling, we can use
that too.
> It's not our language to rename, though, so either the creator OKs it
> or it goes. If there's an acceptable alternative spelling, we can use
> that too.
The web site in the README in the parrot sources uses 'bf', as does at
least one of the sites referenced from there.
--
Andy Dougherty doug...@lafayette.edu
bf it is, then. We'll get that dealt with in the repository.