Perlmonks are so... excellent. Thank you (Your Mother & liz) for exposing my ignorance gently. I didn't know we could timtowdi old syntax. How far does it go? I've done some reading but not that Perl 5 code can be dropped into Perl 6.

> sigilless variables (yes, Perl 6 haz them)!

Is that good? I thought barewords were bad practice. It's been pounded into our heads not to use the old global open FILE convention so now we write open my $file. I realize the implementation is problematic but the original logic of uppercase bare filehandles seems sound considering their relation to STDIN and friends. Is Perl6 going back to the future?

> There is nothing at all stopping Perl 5 from success today except a lack of applications;

That could change overnight. There's an absurd amount of raw power in the Perl ecosystem. What if we decided to deploy as much functionality of CPAN as possible into something like http://blogs.perl.org/users/yang_bo/2018/04/a-new-linux-distribution-with-perl-as-its-heart.html? I'm sure it would rock.

> and general inability to compile or deploy directly to mobile.

Why is that? Does TPF need to fund a grant? How hard is it?

github.com/mid1221213/perldroid
www.corion.net/talks/perl-on-android/perl-on-android.en.html
blog.thireus.com/how-to-install-ios-perl-framework-on-iphone-ipod-touc
+h-or-ipad/
[download]

> If no one had stepped up

Perl 5 has evolved very nicely thanks to its modular architecture.

> the game and its rules

This place has the best referees :-)

Perl 5 will not go away. Perl 6 won't go away either. They are both the result of a Perl mindset.

I guess it doesn't matter, sorry for the rant https://github.com/niner/Inline-Perl5

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.