I don't think it contributes to the conversation to point out that when inexperienced-by-trade people (managers typically don't code) observe inexperienced-by-laziness people (devs who don't learn how to write maintably in any language), they walk away with impressions that have zero correlation to reality.
Especially when they conflate two completely different languages to boot.
There's nothing to take away here other than "some people are beyond being helped".
The parent's question was whether a more enterprise-like web-site would help with Perl6 adoption - I simply said (for our organization) that the answer was no and included a brief description of why that was the case.
In many cases, Java is still considered THE enterprise language. Other languages have invaded that enterprise dominance by running on the JVM. This includes languages like Scala (which was designed for the JVM) and languages like JPython (which was obviously preceded by Python). So here's another question - Would Perl6 adoption in the enterprise be enhanced by compiling it to bytecode and running it on the JVM?
As an aside, my original note admitted that it was at least partially developer practices that led to the excoriation of Perl - that doesn't change the fact that it is no longer acceptable for application development at my workplace.
> Java is still considered THE enterprise language. Other languages have invaded that enterprise dominance by running on the JVM. This includes languages like Scala (which was designed for the JVM) and languages like JPython
I'm always interested to know whether Groovy runs in your JVM workplace, and whether just for scripting, or if you build actual applications with it.
Especially when they conflate two completely different languages to boot.
There's nothing to take away here other than "some people are beyond being helped".