Comment Re:Perl analogue (Score 1) 438
{binmode STDOUT,"utf8";print chr(9585.5+rand);redo}
{binmode STDOUT,"utf8";print chr(9585.5+rand);redo}
I also created a Facebook event for those that use that.
Get off my lawn! grumble grumble.
Saw the doctor? Noted. Diagnosis? Noted.
Noted, but not as open records, c.f. HIPPA privacy rules.
"'There's a societal ideal that what you read is nobody else's business,'"... no, no there isn't.
When speaking about the act of reading, there is some expectation of privacy, at least from the government. This isn't related to businesses per se, but librarians have fought to keep library records private and as such, their policies and software try to keep records for only as long as necessary (e.g. the duration of loan). Librarians often refuse to give out information on their patrons unless there is a court order.
This same sort of ideal can be applied to businesses in the form of opt-in data mining, but U.S. society needs to make this sort of decision in the form of information privacy law.
Wikipedia is good for use as a URL representing a given real-world subject. For example, an article about graphics in Linux could refer to "this DRM, not that other DRM"
Which is why DBpedia (which is based on Wikipedia) plays such a central role for Linked Data.
As far as the matching capabilities of Perl 6, I think they're trying to do something that will advance the state-of-the-art in terms of programming langauge integration in the same way that Perl 5's regex did. The Perl 6 rules are similar to the tricks and hacks that people do with regular expressions to build up full grammars. By separating out the parts into logical components, you will get better readability and reusability. Not only will we get cleaner text processing, but this (along with the VM architecture) will aid the development of DSLs that will extend the language into an exciting future.
Yeah, it's some good Kool-Aid and the Perl community been waiting for a while, but bringing these ideas into a production-ready language isn't trivial. I'm still using Perl 5 because of CPAN, but I feel that Perl 6 will eventually get to the same level especially with a source-to-source compiler. The hardest part would be dealing with native-code bindings.
Saliva causes cancer, but only if swallowed in small amounts over a long period of time. -- George Carlin