A carefully balanced quantity of DWIM (Do What I Mean) without too much WAT, while having awesome error messages to help you get going and continue to be productive.
1,154 karma · joined January 23, 2018
A carefully balanced quantity of DWIM (Do What I Mean) without too much WAT, while having awesome error messages to help you get going and continue to be productive.
say foo-bar - bar-foo;
which would improve readability as well!TL;DR; - my modules had been up for adoption for *YEARS* already, but nobody was willing to take over maintenance - you can *NOT* just remove modules from CPAN. You can only schedule them for deletion after a week - during that period, no alarm bells started ringing that modules that had downstream dependencies, were being completely removed - I knew that my modules would always be available on BackPAN, and that it would be just a matter of someone re-uploading them and adjusting the master list. Annoying at best, because it would not be breaking anything that was already in production. - And I still had my own copies, so if anybody would have asked to please upload them again, I would have. Nobody did.
What this showed, is that CPAN has a definite vulnerability in this area: - someone (hopefully the owner) can schedule all modules for removal - if these modules have downstream dependencies, then that's too bad: they will stop working
Now, almost two years later, this vulnerability still exists.
As to the reason of me removing my Perl modules: it signalled my leaving the Perl community for good. Before that, I had still hope that some day, I actually would enjoy being part of the Perl community again.
Should I not have removed my modules like that? Well, I don't know how I could further indicate that I did not have any desire to keep maintaining them. The ADOPT-ME status was clearly not enough.
As far as the Raku CAT is concerned, he is now serving his "sentence" of being banned, until Jan 1st, 2022. We will see what happens after that. I sincerely hope that the Raku CAT will not have to address any reports about him after that date.
Mr. Trout was made aware of the upload by Mr. Spek. An upload that had been superseded within half an hour by another one without the offending (empty) directory. With the original upload marked for removal, but since PAUSE doesn't let you remove modules immediately, it stayed up for a week. And *ANY* module ever uploaded to CPAN, stays on BackPAN for historical purposes. Which I think is a good thing, so we can see what we're talking about.
Mr. Trout, in his self-assumed role of moderator of the then #perl6 channels, kickbanned Mr. Spek without further ado from the #perl6 channels. Even though Mr. Spek was a regular contributor to the Perl 6 project and user of these channels for asking questions and giving answers. In an ironic way very similar to Mr. Trout. Who, by his own admission, has made *MANY* mistakes, yet until then, was *NEVER* banned from anything in the Perl community.
I considered the action of Mr. Spek more as trolling / stupidity / bad habit / young foolishness at the time. And the first offence to my knowledge, by no means grounds for a permaban on the channels as instated by Mr. Trout. I therefore, on behalf of the core team and after conversations with our de-facto BDFL Jonathan Worthington, asked Mr. Trout to raise that ban. Which in the end he reluctantly did. And since then has been interpreted by Mr. Trout as condoning racism.
Sadly, over time, it has become clear to many that Mr. Spek is either too stupid to realize what he's doing with his trolling (saying he is a proponent of free speech and using that), or indeed a racist at some level, or both. The commit in his personal repo (which he makes public as good examples of using dot files) was about using the "master" branch as the default for new git repos, rather than the current git default of "main". With as single comment "Get a job, N*". This was no longer a use of the word as just a word: this was adding context and meaning. For which the Raku CAT team has banned him from public Raku places and revoked all of his commit bits until Jan 1, 2022.
Meanwhile, it looks like Mr. Spek will not change.
As to Mr. Trout: I will no longer interact with Mr. Trout in any way, shape or form. With pain in my heart, I must say that I've given up on the Perl community. And I say this is a recipient of a White Camel award, awarded for services to the Perl *community*.
I'm not the only person who left the Perl community because of Mr. Trout's antics. I guess in the end, only people willing to put up with Mr. Trout, will be left in the Perl community. I sincerely hope they will be happy, as life is too short to be unhappy without good reason.
The fact that this may or not be true, doesn't matter to him. Nor that he damages the Raku community with this (as well as the Perl community).
However, that this even applies to TPF / the Perl community, is mostly mr. Riedel work, using this trolling for his own agenda (which is reforming The Perl Foundation). The matter has been dealt with within the Raku community already. And Mr. Riedel should know that.
Now, there is that final 10%. Whether the committer knows this or not, he does show some other tendencies that could be considered racist. But in a country like the Netherlands, that is still trying to deal with "Zwarte Piet" (https://en.wikipedia.org/wiki/Zwarte_Piet) this is sadly not as uncommon as it should be.
And she has terminated her relationship with the committer.
The toxic element to be "purged" from the Perl community, has now returned and will make the Perl community more to his image . Which will only get more people to leave the Perl community. But that is no different from the past 15 years that I have had the pleasure of dealing with this toxic element.
This was not stated by McVey, but by me:
> "I'm fresh out of ideas with regards to handling the toxicity in the Perl community," Mattijsen told The Register, "I'm doing my best to make sure that the Raku community will not allow individuals to create a toxic atmosphere without being challenged for what is now decades."
In Raku speak:
my $house = House.new;
my $houseboat = $house but Boat;
See: https://docs.raku.org/routine/butThere would be no need to de-compose.
Perhaps it could be released as Perl 11! (https://web.archive.org/web/20190730071149/http://perl11.org... )
May I point out that basically nobody of the then Perl 6 team (except Jonathan) is currently involved in the development of Raku? So please don't transfer your mistrust to these people: they have no beef in this.
But it's categorically untrue that Parrot wanted to get rid of P6 or considered P6 an afterthought or wasn't willing and able to be receptive to P6's needs, and I'm disappointed that that untruth continues to persist.
Well, maybe I don't have anything meaningful to say about this, as I have no firsthand experience in the matter. So the only thing I can do in this case, is trying to be technically correct.
I believe you had the best intentions towards Parrot and towards Perl 6 (which for some reason you keep mentioning as P6 in your replies). But, for whatever reason, it did not work out. We can keep discussing the past in that respect, but I'd rather work on the future instead.
If you really want to get the history straight, I'd suggest to write a book about it, similar to http://friendlyorangeglow.com which taught me a lot about the people developing the system I grew up with. Good and bad.
I'd say, it turned out to be more difficult than expected?
You haven't addressed my point that NQP yanking the rug out from most other languages running on Parrot harmed Parrot. That seems like a material concern.
I guess I don't understand how NQP would be yanking the rug out from other languages, technically speaking? That it could be seen as a vote of no-confidence: well such is life in the open source world.
You haven't addressed my point that I personally spent multiple months offering to make Parrot better fit NQP/PCT for P6 and was repeatedly rebuffed.
Not having been around at that time, I don't think it is up to me to address that point. If you were rebuffed, I can only surmise that interpersonal and technical relationships had already soured enough not to trust the validity of your offer. Note: I'm not saying that the intent of your offer was questioned.
I don't think that I ever implied that. To me, in one sentence, it's more like "Parrot and Perl 6 diverged, so that Parrot was no longer a good fit for Perl 6, so the Perl 6 developers had no choice but to write their own VM"
If Parrot had provided all that Perl 6 needed at that time, I don't think the multiple backend strategy would have been selected. Why would one?
> where I said that the NQP strategy was going to leave Parrot developers in a dead end
To me that feels like a self-fulfilling prophecy. Also, had Parrot been able to attract other languages to a significant extent, the abandoning of Parrot by Perl 6 would not have been an issue.
Personally, I think Parrot was not able to attract other languages because:
1. it didn't provide enough benefits to account for the extra effort needed by language developers. It definitely did not for Perl 6 at the time.
2. it didn't have a core team welcoming enough to keep anybody vaguely interested in Parrot
In the end, it is always about being able to create a community in open source. Without it, a project is indeed on a dead end.
I just know second-hand that something broke the trust between the Perl 6 and Parrot developers around the first Rakudo Star release. And that strengthened the notion that another backend for Perl 6 was needed.
> I know this contradicts the official Raku hagiography
OOC, which official hagiography are you referring to?
Also, I find the use of "hagiography" in relation to Raku a bit strange: if anything, with the rename, the last saint has basically left the building?
1. Parrot was initially intended to be the backend for Perl 6. 2. Perl 6 didn't materialize fast enough, so Parrot started focussing on hosting other scripting languages. 3. Parrot decided to become the backend for all scripting languages. 4. Parrot became less and less targeted towards Perl 6. 5. Parrot never really became a backend for any other scripting language. 6. Parrot became decicedly a poor fit for Perl 6. 7. Jonathan decided that maybe the JVM could also be a backend, and started porting 8. Building on that experience, Jonathan decided that they could write a dedicated backend for Perl 6, which became MoarVM 9. Parrot development dwindled to effectively 0. 10. During the Great List Refactor of 2015 (about 6 months before the first release) it became clear that porting the Parrot backend would be a lot of additional work, with no apparent upside 11. Parrot support was dropped before the first official release