3 ms·
Unfortunately I cannot recommend the parrot backend for production use yet. We recently found a serious GC bug which is reproducible under very tight memory con
by rurban 12y ago
Unfortunately I cannot recommend the parrot backend for production use yet. We recently found a serious GC bug which is reproducible under very tight memory constraints, such as my mips box with 256MB RAM or with very big perl6 modules.
I'm working on it for a week already and cannot promise to be finished until Jan 31, 2015.
But the other 2 backends, jvm and moar, are doing fine.
- lazyloop 12y agoParrot should just be abandoned, MoarVM is the way to go.
- rurban 12y agoIf you care about small perl6 apps, which do not have to scale with concurrent CPUs, yes. But parrot has a much bigger scale. And lock-free threads.
- raiph 12y agoLarry Wall is not saying P6 will be declared "officially production ready" on Jan 31st 2015. He's saying the devs are aiming to declare that sometime in 2015, quite plausibly Dec 1st 2015 or somesuch.