6 ms·

"I count 33 synoptic documents at perlcabal.org. Synopses 2 through 6 tend to be fairly stable, although changes still occur. The remainder of the synopses are

by jbellis 16y ago

"I count 33 synoptic documents at perlcabal.org. Synopses 2 through 6 tend to be fairly stable, although changes still occur. The remainder of the synopses are still drafts for the most part, awaiting more feedback from implementations and language use." This is why when people like chromatic invariably comment in a "still waiting for perl 6 thread" that "you can write perl 6 now!!11!" I roll my eyes. (Quietly. So they'll go away.)

perlgeek 16y ago
That's not what I call "quietly", fwiw.
ekiru 16y ago
I'm not sure how much Perl 6 chromatic writes on a daily basis (I'm mostly only familiar with his work on his book and the Perl 6 book and his magical ability to constantly find another 2-6% performance improvement for Parrot), but there are quite a few people writing Perl 6 already. Obviously there are people working on Rakudo and other Perl 6 implementations that spend their time writing Perl 6. But there's also people writing wikis, NES emulators, testing tools, build systems, and many other things in Perl 6. When people like chromatic say that you can write Perl 6 now, they aren't speaking based on hypotheticals or beliefs; they're speaking from experience. And, in my personal opinion, despite the NYI status of some things, bugs in the implementations of other things, and slow performance, writing code for Perl 6 is an amazing and wonderful experience. No, I wouldn't rewrite mission-critical systems on which people's lives depend in Perl 6 yet. Yes, I might write systems on which my life and future depend in Perl 6 right now. I definitely would and do write my side projects and one-off scripts in Perl 6 right now.
mst 16y ago
People can, and are doing. Much though I'm a happy perl5 programmer, I often use bleeding edge libraries in my implementations when I'm sure that's the best approach (and if it's code for a client after careful consultation with them). People I know doing rails work often use stuff they know may change under them because it lets them ship faster now and they consider it an acceptable trade-off of risks - and the gems they're using generally don't have a spec document at all. There are risks involved in every technology choice made for every program. If I didn't actively prefer perl5's semantics and community philosophy in a number of places, I'd be seriously evaluating perl6 for use in code where I could guarantee deployment to be pinned against a particular runtime version, just like I -do- use API-unstable perl5 libraries where I can guarantee deployment against a particular library version and the benefits in terms of delivery time outweigh the risks.
chromatic 16y ago
This is why when people like chromatic invariably comment in a "still waiting for perl 6 thread" that "you can write perl 6 now!!11!" I roll my eyes. Almost five years ago now I ported a piece of Perl 5 code used millions of times a day to Perl 6. Where is the hyperbole in my statements?
- koenigdavidmj 16y ago
  Well, you can't just leave us hanging like that. What's the program?

by jbellis 16y ago

perlgeek 16y ago

That's not what I call "quietly", fwiw.

ekiru 16y ago

I'm not sure how much Perl 6 chromatic writes on a daily basis (I'm mostly only familiar with his work on his book and the Perl 6 book and his magical ability to constantly find another 2-6% performance improvement for Parrot), but there are quite a few people writing Perl 6 already. Obviously there are people working on Rakudo and other Perl 6 implementations that spend their time writing Perl 6. But there's also people writing wikis, NES emulators, testing tools, build systems, and many other things in Perl 6. When people like chromatic say that you can write Perl 6 now, they aren't speaking based on hypotheticals or beliefs; they're speaking from experience. And, in my personal opinion, despite the NYI status of some things, bugs in the implementations of other things, and slow performance, writing code for Perl 6 is an amazing and wonderful experience. No, I wouldn't rewrite mission-critical systems on which people's lives depend in Perl 6 yet. Yes, I might write systems on which my life and future depend in Perl 6 right now. I definitely would and do write my side projects and one-off scripts in Perl 6 right now.

mst 16y ago

People can, and are doing. Much though I'm a happy perl5 programmer, I often use bleeding edge libraries in my implementations when I'm sure that's the best approach (and if it's code for a client after careful consultation with them). People I know doing rails work often use stuff they know may change under them because it lets them ship faster now and they consider it an acceptable trade-off of risks - and the gems they're using generally don't have a spec document at all. There are risks involved in every technology choice made for every program. If I didn't actively prefer perl5's semantics and community philosophy in a number of places, I'd be seriously evaluating perl6 for use in code where I could guarantee deployment to be pinned against a particular runtime version, just like I -do- use API-unstable perl5 libraries where I can guarantee deployment against a particular library version and the benefits in terms of delivery time outweigh the risks.

chromatic 16y ago

This is why when people like chromatic invariably comment in a "still waiting for perl 6 thread" that "you can write perl 6 now!!11!" I roll my eyes. Almost five years ago now I ported a piece of Perl 5 code used millions of times a day to Perl 6. Where is the hyperbole in my statements?

koenigdavidmj 16y ago
Well, you can't just leave us hanging like that. What's the program?