I have been a software professional since I was in high school in 1998. I'm enthusiastic about open source, and I really enjoy working in unusual software systems or within strange constraints.
I would not call it a conflict, but a discussion, the basis of opensource development.
What people forget is that opinions are not rules and should not be thrown at each other's face, behavior I've seen in many communities :(
In my opinion, the camel should be simplified and used as Perl's logo due to its history with the language and also due to its characteristics connected to the language itself: funny, "weird" (at first glance), chill, hella strong&resistant, walk miles and miles without eating or even drinking water! I'm not sure how the Raptor was conceived, but I don't see how it represents the language like the camel does.
I have been a software professional since I was in high school in 1998. I'm enthusiastic about open source, and I really enjoy working in unusual software systems or within strange constraints.
Yeah, I tend to think that this isn’t as important a task for an open source project.
I don’t know why everything needs to be a conflict, though.
I would not call it a conflict, but a discussion, the basis of opensource development.
What people forget is that opinions are not rules and should not be thrown at each other's face, behavior I've seen in many communities :(
In my opinion, the camel should be simplified and used as Perl's logo due to its history with the language and also due to its characteristics connected to the language itself: funny, "weird" (at first glance), chill, hella strong&resistant, walk miles and miles without eating or even drinking water! I'm not sure how the Raptor was conceived, but I don't see how it represents the language like the camel does.
Yeah; I have a hard time forming too strong an attachment to a logo for a programming language.