Live data from Hacker News

Perl 6 Optimism

p6weekly.wordpress.com

61–70 of 243 posts

Re: Perl 6 Optimism

#61
post #51

Is anybody here using perl 6 in production at the moment? Or perl 5 for that matter?

If you would have actually read the blog post, you would have seen a "Rakudo Perl 6 in production" section in it.

The section in which obscure companies are using it for trivial tasks?

Sorry if that sounds harsh but in Python, Ruby, even Perl 5 large companies that bet the farm on the language are ten a penny

Re: Perl 6 Optimism

#62
post #58

how would one describe Perl 6 type system? Is it dynamically typed, optionally typed, statically typed?

It has optional static typing:

    > sub f(Int $x) { $x + 1 }
    sub f (Int $x) { #`(Sub|140221097113944) ... }
    > sub g(Str $x) { f($x) }
    ===SORRY!=== Error while compiling:
    Calling f(Str) will never work with declared signature (Int $x)

Re: Perl 6 Optimism

#63
post #42
post #30

Earlier quoted context omitted.

I disagree. To me Perl is more readable than Python. What is so modern about Python? It was released in 1991.

Compared to Perl, the overall under-use of special characters and the forced indentation make it objectively more readable; there is a reason it's often compared to pseudocode. Age of release is a meaningless metric, btw. For starters, what Python was in 1991 is very different from what it was in the early 2000s, when it reached critical mass. Its modernity is measurable by the influence it had on most languages desi…

> Its modernity is measurable by the influence it had on most languages designed after its success, like Go and Swift.

So you are measuring "modernity" by legacy?

Also, I don't see any Python influence in Go and from the brief exposure I've had to Swift, I'd say there isn't much influence there either.

By your axiom, one could argue that C is a modern language.

Re: Perl 6 Optimism

#64
post #40

I spent a huge amount of time in my 20's writing Perl 4 & 5 scripts. Even though I no longer use Perl, I still feel nostalgic about it. That said, I can't find any reason to pick up Perl 6 and start learning it. With so many other useful and interesting languages out there: Python, Elixir, Elm, Rust, etc... what appeal should Perl 6 have to the masses these days? Is anyone jumping into Perl 6 like they did with Ruby…

Actually, I've been looking at Perl 6 and I think it's quite amazing. It's really the only language outside those I get paid to work with that I've considered doing a deep dive on.

I'm not really understanding the lack of love for Perl 6 unless it's from folks that have invested careers in Perl 5 and are miffed by the compatibility story.

For example can someone point to the analog of this https://docs.perl6.org/language/grammars in Python, Ruby, Groovy etc?

Also, https://modules.perl6.org/ seems to be growing.

Re: Perl 6 Optimism

#65
post #42
post #30

Earlier quoted context omitted.

I disagree. To me Perl is more readable than Python. What is so modern about Python? It was released in 1991.

Compared to Perl, the overall under-use of special characters and the forced indentation make it objectively more readable; there is a reason it's often compared to pseudocode. Age of release is a meaningless metric, btw. For starters, what Python was in 1991 is very different from what it was in the early 2000s, when it reached critical mass. Its modernity is measurable by the influence it had on most languages desi…

To me python and perl and two extremes. Perl is almost comical with its use of special characters (which they've embraced even more in Perl 6 with the optional use of unicode symbols in built-in operators) but python went too far the other way IMO. "It looks like pseudocode" sounds nice in theory but people don't typically write huge projects in pseudocode. I don't really like the significant indentation but my main problem is with the awkward scoping rules. I also find that it makes it harder to refactor code (if I copy/paste a snippet at a different level of indentation I can't blindly trust the editor to re-indent it properly).

That being said I agree that these days the tendency across all languages is to go towards fewer special characters, not more. In this context Perl 6's syntax feels a bit anachronistic.

Maybe you'll be able to win a few new user by telling them that in Perl 6 they can use × for *, Ⅻ for 12 and [unicode atom symbol]++ (ironically HN automatically removes the actual symbol when I submit) for atomic incrementation but I expect that many more will recoil in horror. I won't even talk about »=» and the ascii equivalent >>[=]>>.

Re: Perl 6 Optimism

#67
post #20
post #18

Earlier quoted context omitted.

The failure to admit it was going slowly was another killer. It will be released at Christmas, we just aren't telling you which one. After a few years of hoping, I gave up and am in the world of Python and Django. Its a shame as Perl feels like a more powerful / expressive language than Python.

This. Being "forced to use Python" sucks as a Perl developer.

On the flip side, being forced to use Perl always sucks.

I mean it only as a half joke, unfortunately.

Re: Perl 6 Optimism

#68
post #4
post #2

I don’t understand why Perl 5 and 6 are still tied together as if they are the same language. There’s no compatibility between the two. You can’t write a library that works in both versions, so you lose CPAN and the thousands of packages that make Perl so powerful. I don’t think there’s even any reliable way to translate Perl 5 source code. This is a vastly larger change than python 2->3, and people are still using p…

Should have chosen a different name for the language.

A new name would have kept momentum in Perl 5 and it would have made Perl 6 more sexy. It is sad, Perl is amazing, I still use it as my personal scripting language. Back in the day I wrote complete enterprise applications.

Re: Perl 6 Optimism

#70
post #59
post #12

Earlier quoted context omitted.

Why not? It's a neat way of showing off fundamental Unicode support, and AFAIK there are ASCII equivalents for all of them, in case you have no idea how to enter ⤐ or whatever.

Well, this way you will have 2 versions of code in the wild, ascii and non-ascii. We will need to memorize both, which makes it harder to learn, and also having 2 versions of syntax that you run into puts unnecessary mental strain on a developer having to switch between contexts. Perl's motto was always "There's more than one way to do it", but IMHO it was also the root of many of its weaknesses. It just makes code m…

> Perl's motto was always "There's more than one way to do it", but IMHO it was also the root of many of its weaknesses.

So are you suggesting that Perl should discard its TIMTOWDI philosophy? It won't be Perl anymore then, would it?

Post reply on HN