Paging TOBYINK
This week marks 2 years since TOBYINK seemingly dropped off the perl map, in terms of viewable open source contributions that is. Since then the author's modules have gone unmaintained, consequently they are no longer compatible with recent versions of perl. This is going to cause problems eventually.
I, and several others, have sent e-mails to TONYINK but have not received any response. So TOBYINK, where are you? Are you OK? You seem to be active in at least one place? Can you give co-maint on some of your modules that are used or recommended in more widely deployed distributions? Some of your modules are too important to leave to abandonware, and forking them is a path i (and almost certainly others) don't want to take.
Edit: Some non-essential information removed as i don't want to give people bad ideas about compatibility between Moo/Mouse/Moose due to the use in our stack.
Hi, yes I exist. Just busy with other stuff.
Give me a run down of which distributions need fixing.
Hurrah! The [will soon be] critical one is this pull request against Type::Tiny: https://github.com/tobyink/p5-type-tiny/pull/32 # as it will break with the next stable version of perl.
There are other bugs on RT against Type::Tiny, but i don't think they're critical. A few other Types::* dist have some issues but they haven't affected my usage yet.
My offer of taking on co-maint is still open, however to do that i think it would be sensible to have an org on github as i don't want to fork any repos due to existing issues, PRs, etc, that will not be transferred.
Thanks!
Mouse's hopeless incompatibility with Moose is one of the reasons Moo exists. I'd strongly recommend either going straight to Moose or staying with Moo.
The only way to make Moose and Mouse play nice together is, in fact, to go via Moo - if you make an empty Moo role consuming a Mouse role, the Moo role now works with Moose. The Mouse one does not.
Also, consider installing Class::XSAccessor to speed up Moo.
Toby, any chance I can help you get your modules into the moose github org or somewhere else so we can help you with this stuff?
(note that the Moo community is already aware of the problem and were planning to adopt Type::Tiny if tobyink wanted us to, so the current problem is NOT a reason to migrate away from Type::Tiny unless you're trying to support bleadperl rather than actual releases)
-- mst
I'd be interested in seeing your benchmark script to see what you are actually comparing, as some of the numbers seem a bit odd. Also note that MooX::TypeTiny exists and should make the combination of Moo and Type::Tiny as fast as is possible in pure perl. It may be time to bake that in to Moo.
Regarding module maintenance, I had previously tried reaching out about getting comaint or first-come Type::Tiny and some of Toby's other modules. I didn't get any response at the time. We'd definitely be interested in getting Type::Tiny and Toby's other Type- and MooX- dists moved into an org on github (possible the Moose org) and some comaints added so improvements can be shipped easier.
OK, understood - we have two products, one of which is pure Mouse (as per commit message, i.e. no mixing of the streams) and one of which is newer and pure Moo. I'm going to move it all to pure Moose anyway, so the issue is... Moot.
A fork of this: https://gist.github.com/schwern/896004 which i haven't updated other than adding a couple of newer modules and actually updating the dists it's benchmarking. So, possibly wrong/irrelevant?
The benchmarks were a bit of distraction anyway, and just there as a backup in the commit message so i can say "look, faster!" in case the first argument doesn't seem compelling.
lexical::underscore is broken on 5.24, which in turn breaks Scalar::Does and Data::Domain, and probably some other stuff that I've not noticed.
The test failures in Type::Tiny are becoming more urgent as we get closer to the release of perl-5.26.0. There are over 600 CPAN distributions which have first-level dependencies on this module. They cannot be tested against blead until this one test file is corrected.
Thank you very much.
Jim Keenan