why?
a name is not an explanation.
Ava: an XML parser
So for me I repeat is XML support is a bad name.
Look at Comanche, Apache
why apache is not called HTTPServer?
Stef
We can always change it back to YAXO or change it to something else entirely. I would at least prefer something with "XML" in it so people will still be able to easily find, whether through Googling or searching on SqueakSource, an XML parser for Squeak/Pharo/Gemstone without having to know the cutesy name its developers chose for it ahead of time (see practically any Ruby library for an example of what I'm talking about).
Yep. Having 'XML' in the name is important.
Alexandre
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
A name that is not an explanation makes it hard for the user to know what the thing is or does. I have many problems with the Moose / Pharo / Squeak / ... community in this respect: I am sure there are a lot of cool tools and technolgies out there, and I see names flying around but I have no idea what they are.
Apache gets away with it because it is world famous. Once your tool is world famous the name does not matter anymore.
OK name your stuff how you want but in that case the community should also put a glossary online so that people like me can find their way.
On 16 Nov 2010, at 11:16, Stéphane Ducasse wrote:
why?
a name is not an explanation.
Ava: an XML parser
So for me I repeat is XML support is a bad name.
Look at Comanche, Apache
why apache is not called HTTPServer?
Stef
-- Johan Fabry jfabry@dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile