Ask HN: Perl 6: Do you use it, how do you like it, what do you do with it?
Substantial amount of Perl6 goodness is already baked one way or another in ES6&#x2F;7, Python 3.x, Scala and even the modern C# and C++14&#x2F;17. Speaking of stuff like concurrency, C3 resolution, object proxies (a.k.a AUTOLOAD), introspection&#x2F;reflection, promises, reasonable regex engine, etc.<p>As far as speed is concerned - with the modern approach to concurrent programming, it does not really make a difference which of the above languages you&#x27;d choose, as long as your architecture is right. IO::Async may in many scenarious be faster than Node, Perl devs are probably 2x the price of a JS guy...<p>So the question for Perl6 is really - when, if ever, is it going to have tools like npm, make, pip to simplify the maintenance of a project. Not to mention proper debugger (i.e. Perl6 debugging plugin for VSCODE).<p>Perl6 is a lot of syntax even for Perl5 oldies like myself, and I&#x27;ll need a very long list of assurances to convince any client&#x2F;manager&#x2F;colleague to take this road. Because chances are I end up being the only living soul on the planet able to maintain my Perl6 code.<p>After all - R&amp;D is not only about the initial writing (that&#x27;d be 15-20% of all time), but also debugging (huge part), CI (some 15-20%), and post-release support.<p>Unfortunately languages like Scala and ES6 are presently way more appealing with already-complete ecosystems of tools and editors. They also provide pretty much the same performance for likewise non-enterprise projects. On the contrary - in order to introduce Perl6 in an enterprise (where Perl5 is still considered an option), one would have to have a very convincing set of arguments...