"Oh, it took too long to update Perl and now Perl is dead" is true.
"Raku is an interesting new language with some neat features, and excels at this particular type of problem" can also be true. But nobody can hear this message while they keep thinking about Perl.
"Raku is an interesting new language with some neat features..." will be met with "Oh, you mean Perl 6? lol."
If Perl is dead, renaming the last version isn't going to change anything.
Perl6, on the other hand, is effectively another language altogether, and I hope they rename it completely to stop the confusion.
For example, if you find a page suggesting you run 'perl -MCPAN -e shell', and you try using that, you'll probably have a very bad time. Watch out for it trying to upgrade perl itself! There are newer, saner and nicer ways to access CPAN and install packages.
There's also possible conflicts between CPAN and your distribution's own packaged perl modules, but that's a common problem with any software you install yourself rather than through the distro's packaging scheme.
It doesn't mean "no developers or support" because that's at least as true of newly invented languages that HN loves to get excited about. CPAN is a thing and has been for decades.
It doesn't mean "doesn't work, not delivered yet" because there it is.
It doesn't mean "no exciting features" because that's not true either.
It seems to be more of a condemnation than a description. I suspect it's really just a synonym for "passé, uncool, brings back memories of the 1990s I was trying to forget".
It's the same kind of "dead" as Latin: lots of folks actively use it, but meeting someone that does is pretty dang unusual unless you work for the Catholic church, in which case "everyone still uses it, what's dead about it?"
Both have huge problems, perl5 being effectively dead and the most hated language amongst devs. (I'm still trying to save it via cperl though).
And Perl 6 interesting (I was the parrot backend maintainer, until they ditched it), but with no significant future.
Maybe add a few default warnings for using "ugly" features - maybe just in a linter - perhaps not affecting the runtime at all?
One of TypeScript's strengths is that it is JavaScript, but you can configure tslint to help detect certain "bad" JavaScript. Or you can switch on stricter checks (and TypeScript could be just a name for a default list of strict error checks, depending on how you use it!).
For me it's the top goal, but I'm still only at 20%.
Calling this perl7 would have been a huge joke. Renaming the thing also doesn't help with the personnel who is doing the desastrous decisions they did in the last decade. Management need to change, not the name.
JavaScript actually copied its `‘use strict’` syntax from Perl's `use strict;` which in Perl is using a pragma, not a magical string literal that reconfigures the compiler.
You want types? Several systems exist, but the leading implementation is Type::Tiny.
A big part of Perl culture in the late 2000s and early 2010s was focused around rooting out horrible old practices and tutorials, defining good practices, and getting tooling to help. Perl Best Practices came out of in 2005. Some effort to describe these tools and techniques as “modern Perl” followed—check out the inaugural entry of the Modern Perl Books blog from 2009. http://www.modernperlbooks.com/mt/2009/01/
Since Perl5 did what you’re asking for, maybe you should check it out and see what Perl 5 looks like in 2019.