user-pic

Matt S Trout (mst)

  • Commented on Virtual Spring Cleaning (part 9 of X) wherein I retrieve content
    Future:: is a namespace for future implementations and extensions, and your module is going to cause much confusion in its current namespace. I'd suggest maybe HTTP::UserAgent::FutureBased or similar? -- mst...
  • Commented on Overview of current maintainer fails
    There are a number of inaccuracies in this post, not just whether certain modules are maintained, but who the maintainer(s) is/are, and whether they have merged various fixes. This data is not to be trusted and should be considered more...
  • Commented on The removal of the lexical topic feature in 5.24
    The _ prototype failed to be adopted long before the experimental pragma arrived on the scene, much though I guess that doesn't fit the desired narrative. I find it fascinating that in spite of reini's assertions to me on Twitter...
  • Commented on Test2/Test::Builder Update from the QAH
    Oh, chansen, I see you're having a 'yelling at people based on incomplete information' day again (though this comment is still better than our IRC comment telling the new pumpking to 'get your shit together' on his first day when...
  • Commented on The removal of the lexical topic feature in 5.24
    The _ prototype doesn't really help with things like @$ so far as I can see, unless you're saying that I need to rewrite everything that's currently 'foo { ... } ...' to 'foo sub (_) { ... } ...'...
  • Commented on Test2/Test::Builder Update from the QAH
    > I recall there was moves to propose a 3rd way, the "don't integrate yet, but have a way to smooth over our transition more progressively before we finally commit". We've already spent an extra year moving progressively and smoking...
  • Commented on The removal of the lexical topic feature in 5.24
    While, yes, ok, 'any' can thereby use the lexical topic, what about pure perl implementations of similar things using &$ signatures? My problems with lexical $_ have never been exactly core-implementation-related so much as "I have so much code that...
  • Commented on Test2/Test::Builder Update from the QAH
    So far as I can see, in the absence of a viable third way, the options on the table were, basically, 1) Don't merge it 2) Merge it and see what happens, and if necessary unmerge it until we can...
  • Commented on Test2/Test::Builder Update from the QAH
    So, while I've definitely disagreed with Exodist at various stages of the process (FVO 'disagreed' that included at least one fairly lengthy yelling session which, in hindsight, might have been more likely to make him quit than to listen to...
  • Commented on Virtual Spring Cleaning (part 2 of X) in which I release Apache::Tika::Async
    Given Future already supports all of the different loops, as soon as you load an event loop at all it's effectively free. Search::Elasticsearch chose Promises for no particular reason and the author was open to adding Future support as well;...
  • Commented on Virtual Spring Cleaning (part 2 of X) in which I release Apache::Tika::Async
    Dude, please don't call it that! ::Async indicates IO::Async components, which when written using Future.pm interoperate well with the rest of CPAN, including POE, Mojo and provided you bypass the AnyEvent landmine, AnyEvent code too. AnyEvent already tries to break...
  • Commented on A Date with CPAN, Part 1: State of the Union
    Current short version: Use Time::Moment for performance, DateTime for the ecosystem, or Time::Piece for ease of fatpacking. If you want to make CPAN better, a pure perl implementation of Time::Moment or starting to port some of the DateTime ecosystem would...
  • Commented on Uploading a new package
    A perl dist of the form Foo-Bar-Baz-1.23.tar.gz needs to contain a package Foo::Bar::Baz or it will be rejected by PAUSE. This is normally done by adding a file lib/Foo/Bar/Baz.pm that declares the package in the normal way. In the case...
  • Commented on Statistics for perl hash tables
    "What is not good is that the developers have no idea how to evaluate hash tables and there is no sane discussion possible in the mailinglist" Asserting that nobody except you is competent to have an opinion does, indeed, largely...
  • Commented on Some ideas for improving the community - The ANA initiative
    You appear to misunderstand how open source works. "we need" is irrelevant. Actions speak louder than words. Patches speak louder than suggestions. Some of the things on this list are a good idea, some aren't. However none of them will...
  • Commented on Test::More - New Maintainer, Also stop version checking!
    This is awesome to hear. Organisations are an excellent tool and it's nice to see there being more and more of the Catalyst/DBIx::Class/Moose model of open discussion online and on IRC with multiple committers and shared ownership, and to give...
  • Commented on Crowdsourcing self-confidence
    Recruiting for a long standing project with a high barrier to entry and an architecture that's bulging at the seems is hard. During the periods when I've tried to be more active, I've not been able to give out nearly...
  • Posted Hallway++ at YAPC::NA 2013 to Matt S Trout (mst)

    Interested in meeting new people at YAPC::NA? Hallway++ means you're never interrupting

  • Posted An Incident Summary to Matt S Trout (mst)
  • Posted On Codifying Conduct to Matt S Trout (mst)
  • Commented on How do we know when a CORE module is deprecated?
    Petdance, anybody else who happened to be in #perl for the whole conversation will have seen: wasanzy asked for help Shells suggested something that's a really bad idea apeiron corrected this Shells, apeiron and I discussed it until Shells understood...
  • Commented on How do we know when a CORE module is deprecated?
    Steven, it can be preserved on CPAN for the people with legacy code that requires it. Given the existence of Plack::Handler::CGI, starting a new project with CGI.pm in 2013 out of anything except ignorance is simply gross incompetence....
  • Commented on How do we know when a CORE module is deprecated?
    I believe it's leaving core as of 5.22.0 'deprecated' is generally taken to mean "should be avoided because it's been superceded", which CGI.pm very definitely has as of the release of a Plack with CGI support....
  • Commented on How do we know when a CORE module is deprecated?
    Joel, you still don't have any of the context for this, or the help that's been given to wasanzy over the previous weeks and months. I do, however, apologise to anybody who read this blog post before the author fixed...
  • Commented on How do we know when a CORE module is deprecated?
    Coke, Chris Fedde and apeiron have had an axe to grind against each other for years. apeiron decided to put him on /ignore to avoid getting into any more non-constructive arguments. cfedde apparently has gone the "passive aggressive blog post...
  • Commented on Don't release experiments to CPAN
    If it's experimental, I put EXPERIMENTAL (in all caps) in the =head1 NAME abstract section - i.e. =head1 NAME Module::Name - EXPERIMENTAL frobnicator and I think that's useful, just like Net::IRC having 'DEAD SINCE 2004' in the same space is....
  • Commented on no indirect considered harmful
    metadoo, with respect to "Also, objectively speaking, in both cases error messages quite clearly state what has happened", I have to answer with "sure, once you already know what happened". The problem I'm talking about is that the error messages...
  • Commented on no indirect considered harmful
    The real life bug that I've created an equivalent to in that post completely screwed over a critical deployment schedule, and cost me one developer to burnout, one client to assumption of incompetence, and one large codebase to perl. (I...
  • Commented on A perl of your own
    nxadm, I think those people are as served as they're going to get by the capacity to have single-line feature bundles. Getting from 'one line' to 'no lines' requires a trade-off - in this case 'run this using the myperl...
  • Commented on A perl of your own
    nxadm, 'use true;' gets rid of the 1; and MooseX::AutoImmute demonstrates a solution for ->meta->make_immutable (in Moo, immutability happens automatically on first ->new). What I'm looking at here is a way to evolve a set of defaults without needing to...
Subscribe to feed Recent Actions from Matt S Trout (mst)

  • blog.urth.org commented on Test2/Test::Builder Update from the QAH

    Aristotle said:

    Thus the claim that Test modules would have to be written specifically against Test2, in order to be able to work with other Test2-based modules, is simply factually incorrect.

    That wasn't what I was trying to claim. Maybe I don't understand what you and Leon wanted to happen.

    My point was simply that Test2-using tools will not cooperate with code that uses the existing pre-Test2 Test::Builder. Of course, if Test::Builder is using Test2 under the hood, then tools using Test::Builder do not also have to change (but AFAICT no one is say…

  • Aristotle commented on Test2/Test::Builder Update from the QAH
    Maybe I don't understand what you and Leon wanted to happen.

    Yes, sorry, I’ll be publishing a long-form, detailed version of the proposal very soon. I’ve realised the proposal is (either largely or entirely) non-understood – the abridged version I presented on the fly at that table was insufficient. (I had hoped but failed to have it out there sufficiently early before the QAH that people could digest it in detail.)

    My point was simply that Test2-using tools will not cooperate with code that uses the existing pre-Test2 Test::Builder.
  • Chad 'Exodist' Granum commented on Test2/Test::Builder Update from the QAH

    One of the initial options discussed as early as last year was this:

    Test2 and Test::Builder remain separate. Tools pick one a build with it. To use both together you load a shim such as Test2::Legacy, which replaces Test::Builder with the alternative guts.

    This was the alternative being discussed in the Test2 meeting on day 1 of the 2016 hackathon. We decided it was not the right plan. My main reason for opposing this plan is that nothing stops people from updating old modules to use Test2, and also auto-loading the shim to insure they do not break things that depend on them…

  • Tom M commented on Virtual Spring Cleaning (part 9 of X) wherein I retrieve content

    Good to see more people using Futures.

    There's a couple of existing distributions which already provide Future-based wrappers around a few HTTP clients:

    Neither of these is suitable as a truly generic HTTP client API, being intended more as an abstraction for non-streami…

  • Jakub Narebski commented on Virtual Spring Cleaning (part 9 of X) wherein I retrieve content

    Net::Async::Ping also returns Future. I have used it in my fork of wolicious: https://github.com/jnareb/wolicious

Subscribe to feed Responses to Comments from Matt S Trout (mst)

About blogs.perl.org

blogs.perl.org is a common blogging platform for the Perl community. Written in Perl and offering the modern features you’ve come to expect in blog platforms, the site is hosted by Dave Cross and Aaron Crane, with a design donated by Six Apart, Ltd.