key
hook where you know the input is going to be a string than setting up a listener for arbitrary tags in a lot of XML parsers.
Ben Morrow: I have no idea, but presumably because as the Wikipedia article points out the old format couldn't represent all the NSValue
types whereas the new format can.
The old format wasn't easier for humans or machines. When I wrote files in the NeXTSTEP format I had to look at the manual to make sure I was getting the syntax right, with XML I (and my editor) already knew how.
The same goes for machines. Language $foo
already has an XML parser/emitter. It probably doesn't have the same support for NeXTSTEP property lists.
In any case. Bikeshedding the specifics of the format misses the point. It doesn't matter that it's ugly as long as it's uniformly ugly. Uniformity means you only have to solve the problem of reading configuration files once.
]]>
They can't appreciate the power of it as that would require a lot more investment in their part and many, especially those who already come to (back) to Perl with suspition will not want to invest that time.
I think this is natural.
IMHO we should keep doing our respective thing we are good at and also encourage the people who spend their time on making Rakudo and Parrot better and faster.
We should keep showing the qualities of Perl 6 in blogs and other ways.
]]>It is a difficult process developing a new and innovative language.
It is too bad that people don't appreciate the amount of work, which is put into it. Every language needs some early adopters. I hope people pick it up, it would be a pity if it vanished.
Is there something like cpan for perl6? I couldn't find anything like it. I was planning to use perl6 for system administration scripts. It would be nice if it is possible to share libraries in an easy way.
]]>