Re^9: Should I upload it on CPAN?

[stvn]

With respect. Twaddle!

You're welcome.

Using the 300+ modules of Moose et. al.:

You are in love with that number, but you and I both know you are manipulating it for effect. That is the number of individual PM files that it uses, not the number of modules that it installs. Also, Moose is only a small portion of that, MooseX::Declare and PPI play a large role in that list, neither of which are Moose. (no no, MooseX::Declare is not Moose, don't get me started on that).

... invoke LWP::Simple::get() on a list of files, write them to a temporary directory, and then invoke system to run a command; is an inappropriate use of abstraction. The creation of complexity from simplicity. In a word, overkill.

Sure, thats fine, I won't really argue that point, but once again you seem to forget, Moose is not to blame for the overkill, the author is.

Like hiring the Philharmonic Orchestra to play musak in your lift; using an 18-wheeler to fetch a pint of milk from the corner shop; deploying the Delta Force to remove a spider from your bath.

1. World's most awesome elevator ride! (although perhaps a little crowded)
2. Nothing says "cool" like a Big Rig! Thats a big 10-4 good buddy!
3. Spiders are scary, THEY HAVE EIGHT EYES!!!!!!

With regard to expertise: Still no one has stepped up to decipher this diarrhoea:

Not publicly no, but honestly this is why I recommend against MooseX::Declare because it does f*cked up stuff like this to otherwise normal code.

If you need what Moose provides, and if it works, it's really cool. But it doesn't always work right, and when it doesn't, you are world of pain. Up shit creek without a paddle unless some one-of-the-four takes pity on you. And that is no way to make a living in this industry.

Wow, that is a pretty harsh words for which you have absolutely no basis. Moose works very well for hundreds, if not thousands of developers every day, if it was as fragile and dangerous as you think then it simply would not be being used.

[BrowserUk]

but you and I both know you are manipulating it for effect.

No. I am not. It is derived exactly as you see it. (That's exactly why I posted the code showing how it was derived; so I could not be so accused.)

Does it represent just that subset of the Moose* you (perhaps uniquely) know to be the body of Moose. Apparently not, (though how would I know?), it comes attached to a full spread of rutt-time antlers.

I appreciate the distinction which you've made before, but just as the good bits of rap (some jazz-rap fusion is astonishingly good), have a hard time segregating themselves from the less salubrious parts of the genre, that distinction is a very hard line to draw when installing other people's packages.

once again you seem to forget, Moose is not to blame for the overkill, the author is.

Actually, you are forgetting that in this thread, I was not attacking Moose. I was attacking the overkill of its use for the module in question.

... awesome ... "cool" ... scary ...

These words are not a part of my vocabulary when deciding the appropriateness of the use of technologies.

Wow, that is a pretty harsh words ...

When you step into a fight with all guns blazing, don't be surprised if the incumbents turn their firepower in your direction.

... for which you have absolutely no basis.

And yet, there it is, and remains, unanswered: a 176 line error message.