demerphq oryiufjngmailcom 101307 chromatic wrote friday 12 october 2007 191055 pagaltzis wrote chromatic 20071013 0005 friday 12 october 2007 133650 pagaltzis wrote hate bring im particularly fond dumping perl6 compare effort going python 3000 track record took internal refactoring juggling ok break backcompat approach vs complete retink approach perl6 clearly problem perl 6 daddy googlebucks funding 20 50 development time sorry single partiallyfunded developer working year capable delivering volunteer work gone pugs multiple backends several years thats bogus think rather clearly problem resources quality fixed place time free variable scope knob one turn obviously dialed lot py3k project keep time variable exploding point python 3000s resources knob settings higher 15 sadly perl 6 perl 5 knobs stuck combined several years count correctly person actually spending dayjob time working perl 5 6 official blessing employer jan maybe rafael missed year worked fulltime perl included employer admittedly started working new job writing book moving house contributions dropped zero thats life comment thread im aristotle seems tendency perl circles take position two possibilities work perl6 totally new language b maintain perl 5 0 tolerance backcompat breakage think middle ground try keep much perl5 possible focus cleaning internals things perl5 must sacrificed achieve include xs code things isnt binary scenario people choice perll5 versus perl6 options think kurila belong list time proves another choice said im super keen kurila dont think aimed problems think hold perl5 back mere existence proves options conventionally postulated think reminder important community personally think start thinking outside box bit might realize perfectly viable future perl5 doesnt involve slavishly devoted backwards compatibility isnt called perl6 yves perl mredebug e justanotherperlhacker wed 06 aug 2008 120847 0200 kurila 13 released