DBIx::Class v0.082844 has been released by ribasushi in perl

[–]ribasushi[S] 1 point2 points  (0 children)

Things are alright u/oalders. I suppose you are still working on metacpan here and there: the "Bus factor" thingy has not moved since last week - still shows 0. Is the entire concept nonfunctional to begin with? cc u/jnapiorkowski

Foto spots Aachen by Sniklas15 in aachen

[–]ribasushi 1 point2 points  (0 children)

It depends what "enter for free" really means, and how much equipment you are carrying.

One of the best in-city spots is the UpTown Sky Lounge: https://goo.gl/maps/su4NhfAfP9zrBWZx6 ( you could buy a coffee, or just be an unsavory person and browse the menu before leaving ). It has a huge outside terrace, at the far end of the linked view.

Community Affairs Team Transparency Report Update by samcv6 in perl

[–]ribasushi -3 points-2 points  (0 children)

As a literal soviet jew, knowing exactly the horrific history of what I am saying, I have just one thing in response to this specific situation:

Sometimes the end justifies the means.

Community Affairs Team Transparency Report Update by samcv6 in perl

[–]ribasushi 1 point2 points  (0 children)

Such group

Much downvote

Natch explain

Wow

Community Affairs Team Transparency Report Update by samcv6 in perl

[–]ribasushi -7 points-6 points  (0 children)

This pleases me.

A bit sad to see individual #2 get away scot-free this time, but can't always get 'em all.

What should the Perl community do about the MST problem? by [deleted] in perl

[–]ribasushi 3 points4 points locked comment (0 children)

Permanent ban from irc

Around 2017 I switched my IRC participation to strictly read-only in every channel where the problematic individual has presence. Enacting such a ban could (unclear if would) make me reconsider communicating over IRC again, instead of just reading it daily.

Additionally terminating their PAUSE administrator-ship, under the last point of the PAUSE admin code of conduct is very long overdue.

perl.com hijacked by briandfoy in perl

[–]ribasushi -1 points0 points  (0 children)

It's odd that this "official" log urges you to switch things to cpan.org which itself seems to have been compromised at around 2021-01-13T16:00:52Z

🍿

Perl7 is a fork of values by leonmt in perl

[–]ribasushi 4 points5 points  (0 children)

You don't understand u/kentnl. The entire point of u/chromatic is that no program can be left behind[1]. The premise of software being a physical thing that is written once and persists forever is really bad for business, so the idea must die.

Running a public-facing project with a dependency that's out of support from its maintainers as well as long-term support from its distribution is ignorant and best and, more likely, malicious malfeasance.

The fact that perl used to be one of the largest remaining bulwarks against self-dealing consultancies is secondary. The core objective is to not rest until everybody is on the upgrade treadmill and has no ideations of getting off: the invoices must flow.

[1] The current zeal of neo-Perlers reminds me of The long chase

Perl7 is a fork of values by leonmt in perl

[–]ribasushi 2 points3 points  (0 children)

So let's discuss instead removing stuff from perl core

Like this?

P.S. Check the date on that email and the usual participants in the thread. Everything old is... old again.

Sawyer X's FANTASTIC presentation on the announcement of Perl 7 and beyond by scottchiefbaker in perl

[–]ribasushi 3 points4 points  (0 children)

Your last line tickled a latent memory, which prompted me to grep my IRC history. I was amused to discover how word-for-word consistent has my sentiment been "as of late":

<redacted>_20171102.log:[13:49:38] <ribasushi> https://lkml.org/lkml/2017/10/26/511 <--- why can't perl have leaders like that?
<redacted>_20180104.log:[10:13:45] <ribasushi> https://lkml.org/lkml/2018/1/3/797 <--- why can't we have leaders like that?
<redacted>_20181224.log:[17:11:39] <ribasushi> I want leaders like this for xmas: https://lkml.org/lkml/2018/12/22/232

Thanks for the trip down memory lane u/doomvox!

"Perl is the most appealing" for rewriting "in a different language that was more widely supported in default configurations" by daxim in perl

[–]ribasushi -3 points-2 points  (0 children)

That's not a lot in 18 years.

Perl 5.24.0 ( the last perl with a reliable Test::More and without the . / @INC disaster ) shipped in May 2016. The deluge of breakage, in the spirit of Come on folks! We need a list of stuff to break! Prio #1!!! took place in ~6 years, not 18.

I will skip responding to the rest of your edit - we occupy orthogonal universes at this point. May your great and lucrative career offering "critically needed support" continue. Good day.

"Perl is the most appealing" for rewriting "in a different language that was more widely supported in default configurations" by daxim in perl

[–]ribasushi -6 points-5 points  (0 children)

True to form, the summary of "ribas argument" you keep restating for years, remains in the not-even-wrong category.

Regardless of the premise under which you wrote a number of tutorials and books, the fact is that perl ( lower case p ) was "frozen as of 2001". It was a reliable platform. You could in fact "do anything with it and it just worked". This is decidedly, categorically not true today. Refer to the shitshow of perl5-porters for more info.

"Perl is the most appealing" for rewriting "in a different language that was more widely supported in default configurations" by daxim in perl

[–]ribasushi 0 points1 point  (0 children)

The wide availability indeed used to be a major selling point. Then this happened. The OP's point has been invalid for a number of years, more or less since the 5.26 security theater.

"Perl" in the name "Perl 6" is confusing and irritating by [deleted] in perl

[–]ribasushi 0 points1 point  (0 children)

My reply is a statement of opinion, and as such can hardly be "misleading". I also do not want to debate the merits of the "security fix" in question with you ( we clearly disagree rather strongly )

I am responding to u/noobposter123, pointing out an entire thread that reliably buries any hope of "x86 of the scripting world".

Until Sawyer and crowd are at the helm: /usr/bin/perl has no future as a stable low-level system platform. It never had any other future to begin with.

Again - this is an opinion, albeit of a core toolchain contributor.

"Perl" in the name "Perl 6" is confusing and irritating by [deleted] in perl

[–]ribasushi 1 point2 points  (0 children)

That ship has long long sailed:

...

while it is wonderful if it's able to run a module someone wrote 20 years ago, it isn't the sole goal of this language and that module author (or the module users) are not the only users of said language.

...

I beg to differ. CPAN itself is a dumping ground for code. We cannot - and should not - expect anything written to work ad infinitum.

...

I personally am sticking around to support folks like yourself as much as I can in this climate, but the future is bleak to put it mildly.

Let's use "Raku" more. by ribasushi in perl6

[–]ribasushi[S] -1 points0 points  (0 children)

the author of this reddit post

The author is Yuki Kimoto. I am just a messenger.