Grinnz

8 ms·

1.
by Grinnz 4y ago
> First, opting in to an experimental feature could be a one-liner, “use experimental feature ‘try’” or similar. There’s no point in punishing your valuable beta testers beyond that with a second line that’s entirely redundant with the f
2.
by Grinnz 5y ago
> That it would be maintained is all that really mattered to me, and there's no doubt in my mind that it would be. Nor mine, but because I know that Perl 7 would die as most of the maintainers stayed working on Perl 5. Or the worst
3.
by Grinnz 5y ago
You were reading between the lines, and the initial announcement was writing between them. But like I said, it is not feasible to maintain a LTS Perl 5 next to a fork of the interpreter. The actual proposal was only even to maintain Perl 5
4.
by Grinnz 5y ago
The original proposal for Perl 7 was good at grabbing attention, but not good at being something that could reasonably be accomplished by the current set of core developers - it would require either maintenance of two forks of the language
5.
by Grinnz 5y ago
Sinking to their level doesn't move anyone forward.
6.
by Grinnz 5y ago
For the record, shitting on other languages does not represent the values of Libera #perl. Though I personally would not use python or PHP, use whatever gets the job done.
7.
by Grinnz 5y ago
The CPAN upload and the commit message are two separate incidents, but to your point, things can be removed from BackPAN through some effort, and efforts are being made.
8.
by Grinnz 5y ago
Only the person who uploaded a distribution can schedule it for deletion, and yes, anyone could do this with currently-indexed versions of their modules. Relying foremost on the goodwill of authors rather than the intervention of PAUSE over
9.
by Grinnz 5y ago
The article has now been updated to correctly indicate that other than Sawyer, these events are specifically regarding TPF and not the community as a whole. Thanks to the author for clarifying things.
10.
by Grinnz 5y ago
My comment saying this on the article has now been downvoted enough to hide it. I guess they don't care about the article making actively false statements like "The Perl community is in a shambles due to disputes concerning its (n
11.
by Grinnz 5y ago
While you're correct, what they "left" is actually a non-programming legal foundation (other than Sawyer X), and so the commenter is actually correct that this ultimately does not have the impact on the Perl community that th
12.
by Grinnz 5y ago
There doesn't, and most of this doesn't actually affect the Perl community or development at large.
13.
by Grinnz 5y ago
This article seems to be highly misinformed. The Perl Foundation is not The Perl Community. Sebastian Riedel and Curtis Poe are still very much involved in the community and development of Perl. Elizabeth Mattijsen and Samantha McVey have n
14.
by Grinnz 5y ago
Some hints (root is rasengan): <root> jane_doe: hint the freenode network is its own sovereign state https://freenode.net/news/taking-irc-further#canceling-cance...
15.
by Grinnz 5y ago
More context: they are in the (slow) process of shutting down servers one at a time and bringing them up running InspIRCd with new Anope services, with none of the old channel or nick registrations.
16.
by Grinnz 5y ago
Curious what makes you think Python will be less susceptible to this, after the whole 2to3 debacle? I'll note that Perl just went through a year or so of painful argument to rediscover that "Perl should stay Perl", so I&#x2
17.
by Grinnz 5y ago
Perl
18.
by Grinnz 5y ago
I don't see this having occurred in either direction. An assertion was made, contradicting details were provided, and then it became emotional due to past interactions.
19.
by Grinnz 5y ago
None of the people directly involved (myself included) are core maintainers beyond the weakest definition of the term, and all of us (including Sawyer) were referencing the stated opinions of actual core maintainers.
20.
by Grinnz 5y ago
There is also a bit of context in the referenced mailing list posts, which are in response to a rationale given for Sawyer's initial Perl 7 plan - perhaps to us, repeating the argument previously used as justification for breaking code
21.
by Grinnz 5y ago
There is, but I'm not aware of the specifics that led to this level of animosity. All I can say for sure is that over the past year or so, there has been arguments regarding Sawyer's initial Perl 7 plan in public and private, and
22.
by Grinnz 5y ago
No one demanded he respond to every rebuttal in detail. Every reply presented alternate evidence which stands on its own without characterization. It was an asymmetrical exchange, but because one of the people involved was an authority figu
23.
by Grinnz 5y ago
There is an adoption process for truly inactive maintainers: http://neilb.org/2013/07/24/adopt-a-module.html - you can also often get somewhere by just asking the current maintainer nicely by email. The timel
24.
by Grinnz 6y ago
It's not my understanding that the "Perl 7" idea suddenly gives license to be backwards incompatible. Instead, features that have been made available and gated in previous releases can be made default in a new major version.
25.
by Grinnz 6y ago
This is planned.
26.
by Grinnz 7y ago
Perl (5) is array-of-codepoint based, at the logical level. Those codepoints might be internally stored as their encoded-to-UTF-8-bytes, or they might not, but this does not affect the usage of the string. Many don't really understand
27.
Perl 5 is now on GitHub(nntp.perl.org)
5 points by Grinnz 7y ago|0 comments
28.
by Grinnz 7y ago
As a Perl programmer, this is basically a post I might have written (aside from knowing it's not dominant anymore :) One more really cool aspect is the first class Unicode support, which Perl can do but you have to work at it.
29.
by Grinnz 7y ago
<> is actually <ARGV>. And actually the least cryptic spelling IMO is "readline(*ARGV)" or just bare readline, which still compiles to the same opcodes. Sure, <> is more common, but it's easier to find what
30.
by Grinnz 7y ago
File::Slurper is just as immediately obvious, and happens to not be fundamentally misdesigned :) Path::Tiny is also great.

More ›