3 ms·

I also enjoyed the article but came away with absolutely no desire to ever use or encounter perl6.

KGIII 9y ago
The 6 is for the number of users. ;-) On a more serious note, your comment is pretty much what I've seen most people say. I will probably poke at it, at some point. I won't have a good reason to do so, except just to learn.
- throwaway7645 9y ago
  There is more than you think and I expect a decent amount of people to come over from Perl5, Ruby, and Python if the language gets optimized enough. Just for small stuff at first, but in larger numbers as the libraries start to show up
inopinatus 9y ago
I was similarly wondering what the killer application, platform, or tool will be. This review calls out the ease of FFI and a reasonable set of concurrency primitives so, in conjunction with the grammars and the data-mangling heritage, I conjecture that Perl6 might be good for IoT programming or SCADA. Of course it's a long trek from "might be good for" to "look at this compelling thing we built with it".
igravious 9y ago
Each to their own. What's your brand of poison?
- breatheoften 9y ago
  Full disclosure: I'm not sure a language called perl will ever appeal to me -- I have amusing post-traumatic life memories of perl. My main perl using/learning experience was back in college for a IT job. I was using this tool called unattended[1] which was about automating windows xp installations ... Involved writing hacky perl scripts to do very hacky things -- with some amount of building on top of somebody else's injected (and in some cases dynamically generated) perl code -- in a context where the only way to run/test changes was to reboot a machine, initiate a complete windows installation, wait for it to finish, and then wait for various post-installation hooks to kick in and eventually get around to running your code... NOT a fun place to learn the many many random subtleties of $ vs @ variable dereferencing behavior or any of the other samples from the long list of surprising perl behaviors ... [1] http://unattended.sourceforge.net/index.php http://unattended.sourceforge.net/index.php I have a lifelong preference for languages which don't actively prefer obfuscation over clarity... If your expectation for your developer's workflow is such that calling a directory 't' for 'tests' is deemed a useful abbreviation -- then I just simply do not want anything to do with that workflow.

The 6 is for the number of users. ;-) On a more serious note, your comment is pretty much what I've seen most people say. I will probably poke at it, at some point. I won't have a good reason to do so, except just to learn.

throwaway7645 9y ago
There is more than you think and I expect a decent amount of people to come over from Perl5, Ruby, and Python if the language gets optimized enough. Just for small stuff at first, but in larger numbers as the libraries start to show up

inopinatus 9y ago

I was similarly wondering what the killer application, platform, or tool will be. This review calls out the ease of FFI and a reasonable set of concurrency primitives so, in conjunction with the grammars and the data-mangling heritage, I conjecture that Perl6 might be good for IoT programming or SCADA. Of course it's a long trek from "might be good for" to "look at this compelling thing we built with it".

igravious 9y ago

Each to their own. What's your brand of poison?

breatheoften 9y ago
Full disclosure: I'm not sure a language called perl will ever appeal to me -- I have amusing post-traumatic life memories of perl. My main perl using/learning experience was back in college for a IT job. I was using this tool called unattended[1] which was about automating windows xp installations ... Involved writing hacky perl scripts to do very hacky things -- with some amount of building on top of somebody else's injected (and in some cases dynamically generated) perl code -- in a context where the only way to run/test changes was to reboot a machine, initiate a complete windows installation, wait for it to finish, and then wait for various post-installation hooks to kick in and eventually get around to running your code... NOT a fun place to learn the many many random subtleties of $ vs @ variable dereferencing behavior or any of the other samples from the long list of surprising perl behaviors ... [1] http://unattended.sourceforge.net/index.php http://unattended.sourceforge.net/index.php I have a lifelong preference for languages which don't actively prefer obfuscation over clarity... If your expectation for your developer's workflow is such that calling a directory 't' for 'tests' is deemed a useful abbreviation -- then I just simply do not want anything to do with that workflow.