Perl 6 -- Too Bloated to Survive? (Core Devs Discuss)
1–10 of 18 posts
Re: Perl 6 -- Too Bloated to Survive? (Core Devs Discuss)
#2the comments are the most interesting part of this. original poster makes lots of assumptions, many of which are challenged by people who know the raduko code.
Re: Perl 6 -- Too Bloated to Survive? (Core Devs Discuss)
#3This is also thoroughly debunked in another article posted here an hour ago or so:
http://www.modernperlbooks.com/mt/2010/07/an-accurate-compar...
Comes across to me like chicken-little syndrome.
Re: Perl 6 -- Too Bloated to Survive? (Core Devs Discuss)
#4This is also thoroughly debunked in another article posted here an hour ago or so: http://www.modernperlbooks.com/mt/2010/07/an-accurate-compar... Comes across to me like chicken-little syndrome.
Here's the HN post referred to: http://news.ycombinator.com/item?id=1563618
Re: Perl 6 -- Too Bloated to Survive? (Core Devs Discuss)
#5Bloated? No.
Needs some optimizations? Sure.
Re: Perl 6 -- Too Bloated to Survive? (Core Devs Discuss)
#6The time is ripe for the next "big" language + framework to come on the scene. I predict it will be a compiled language with rapid compilation and advanced debugging/runtime monkeypatching, such that most of the advantages of dynamic languages will be subsumed. It will also support some advanced way to handle concurrency.
Re: Perl 6 -- Too Bloated to Survive? (Core Devs Discuss)
#7the comments are the most interesting part of this. original poster makes lots of assumptions, many of which are challenged by people who know the raduko code.
Yes the OP comments throughout contain a lot of historical inaccuracies about Parrot & Rakudo.
The ParrotVM team did publish a precise roadmap a few years back and I believe the optimization wasn't due to circa version 3 or 4? (ParrotVM is currently at 2.6).
NB. Unfortunately I can't find the original roadmap I'm referring to at moment because it may not have made the Rakudo move from svn to git?
Re: Perl 6 -- Too Bloated to Survive? (Core Devs Discuss)
#8The time is ripe for the next "big" language + framework to come on the scene. I predict it will be a compiled language with rapid compilation and advanced debugging/runtime monkeypatching, such that most of the advantages of dynamic languages will be subsumed. It will also support some advanced way to handle concurrency.
Add inferred typing and you've got F# :-)
Re: Perl 6 -- Too Bloated to Survive? (Core Devs Discuss)
#9This reminds me of a lot of the "discussion" surrounding the Mozilla project back in the pre 1.0 days.
Non Project Member makes a decent point about performance, but does so in an incredibly presumptuous, entitled, non-helpful way.
Project Members make a lot noise and had waves about pre-production, non-optimized versions, etc., but never come out and say "Yes, version n+1 of our project will most likely use more ram and run slower on the same hardware as version N of our project"
Re: Perl 6 -- Too Bloated to Survive? (Core Devs Discuss)
#10The time is ripe for the next "big" language + framework to come on the scene. I predict it will be a compiled language with rapid compilation and advanced debugging/runtime monkeypatching, such that most of the advantages of dynamic languages will be subsumed. It will also support some advanced way to handle concurrency.
Why do you think "compiled" is the opposite of "dynamic"?