Imo it's very likely the Rakudo team will make this level of integration work reasonably well this year.
On what do you base this opinion? Rakudo's had more than one proof of concept that never made it much past the proof of concept stage before bitrotting before.
It's not secret that a substantial amount of Rakudo development goes toward writing something intended to be a VM abstraction layer. The official party line is "To improve the potential of running on other VM backends".
So yeah, of course some people are still using Perl....
We call that the CPAN, and it's the opposite of plummeted.
Re:Whatever happened to Perl 6?
on
Perl 5.16.0 Released
·
· Score: 4, Informative
If that scares you, cover your eyes: there are more than two compilers.
... it looks like Parrot was dropped.
Not exactly. The Rakudo (Perl 6 on Parrot) people want to write a VM independence layer and port that to multiple VM backends.
Don't ask me to explain that.
Re:Whatever happened to Perl 6?
on
Perl 5.16.0 Released
·
· Score: 5, Interesting
... part of the problem I think is that perl 6 is not ANYTHING like perl 5.
The parts of Perl 6 I like are a lot like Perl 5, and the parts I really like are much better than Perl 5.
... the only reason I still use perl 5 TO THIS DAY is the regex capabilities. They completely ripped that out of perl 6 and re-implemented it to make it more user-friendly, and they did so poorly, IMHO.
I like Perl 6 grammars far, far more than I like Perl 5 regex. That's one of the best parts of Perl 6. Regex as borrowed from Unix and enhanced over the years have accumulated a lot of mutually incomprehensible cruft. Perl 6 cleans that up.
The problem with Perl 6, of course, is that no implementation is anywhere close to practically useful. Almost twelve years after the Perl 6 announcement, there's still no reason to hold your breath.
I think one has to be programming Perl for 40+ hours a week, in order for their mind to stay fresh enough in Perl...
I think you have to understand the two underlying philosophical notions of Perl and know how to use the documentation to use it effectively. The book Modern Perl (I wrote it; electronic versions are free) explain those straightaway.
Garbage collected language runtimes don't fragment memory, or if they do they can clean it up very easily.
It's incredibly easy to fragment memory in a language with GC; see Firefox.
With that said, you can use a copying or compacting GC strategy to minimize the possibility, but then you increase your memory requirements to manage the copy and you reduce your cache coherence.
Slashdot Mirror
On what do you base this opinion? Rakudo's had more than one proof of concept that never made it much past the proof of concept stage before bitrotting before.
It's not secret that a substantial amount of Rakudo development goes toward writing something intended to be a VM abstraction layer. The official party line is "To improve the potential of running on other VM backends".
It can be, yes. The last two times I needed multiprocessing, I used Proc::Fork and WWW::Curl::Simple. These worked very well for me.
A lot of people use AnyEvent quite effectively too.
I've deployed a few projects in the last five years. I know many people who've also deployed projects.
If you're interested in facts, feel free to provide measurements or statistics to prove me wrong.
We call that the CPAN, and it's the opposite of plummeted.
If that scares you, cover your eyes: there are more than two compilers.
Not exactly. The Rakudo (Perl 6 on Parrot) people want to write a VM independence layer and port that to multiple VM backends.
Don't ask me to explain that.
The parts of Perl 6 I like are a lot like Perl 5, and the parts I really like are much better than Perl 5.
I like Perl 6 grammars far, far more than I like Perl 5 regex. That's one of the best parts of Perl 6. Regex as borrowed from Unix and enhanced over the years have accumulated a lot of mutually incomprehensible cruft. Perl 6 cleans that up.
The problem with Perl 6, of course, is that no implementation is anywhere close to practically useful. Almost twelve years after the Perl 6 announcement, there's still no reason to hold your breath.
I have a bias, but I've had many positive responses to Modern Perl: The Book.
Slight plug for ClubCompy, which we're creating to do just that.
Libertables—a salty, prepackaged (but free) lunch food product.
What are you doing that Catalyst has generated thousands of lines of code for you to read?
What have you found that handles Unicode better?
It in fact has three disadvantages: it bypasses any prototype coercions, it passes @_ unmodified by default, and it's unidiomatic.
All of these fencepost errors I've fixed argue otherwise.
Try Moose.
I think you have to understand the two underlying philosophical notions of Perl and know how to use the documentation to use it effectively. The book Modern Perl (I wrote it; electronic versions are free) explain those straightaway.
Could said novice read the documentation?
Install cpanminus from the CPAN then. I do.
Provided a single personal deduction for necessities (and not the $75 annual deduction for sales tax on groceries in states like Idaho), yes.
Good luck convincing even a single taxing authority to enact that, though.
Income tax rates, sure. Let's talk about payroll taxes and capital gains taxes too.
Perl has better type safety than JavaScript. Compare string concatenation in both languages, for example.
It's incredibly easy to fragment memory in a language with GC; see Firefox.
With that said, you can use a copying or compacting GC strategy to minimize the possibility, but then you increase your memory requirements to manage the copy and you reduce your cache coherence.
The Escape key should do it.
How about a web based system? ClubCompy's Tasty language does exactly that.
(Disclaimer: I consult on ClubCompy.)
The roots of the word are normal Greek words for "good" or "well" and "messenger".
I can easily imagine that such organizations have much more dramatic problems than Mozilla's numbering scheme.
... until you do IO.