sub run
{
my $cmd = join(' ', @_);
print "Running: $cmd\n";
system $cmd;
}

...which is helpful to see how far things are progressing, and where things died if something broke in the middle.

Can you elaborate on this?

I've noticed that I had cpanm installed both in $PERLBREW/bin and also in each individual perlbrew's lib - it would be nice to block separate installation, or to symlink back to the original somehow.

Or, just fix the strangeness. :)

Server Side

package Hello;
use base 'Yote::AppRoot';

sub hello {
return "Hello World";
}

1;

Javascript Side

$.yote.init();

var hello_app = $.yote.fetch_app('Hello');

alert( hello_app.hello() );
// outputs "Hello World"

* "My system worked, then I updated CPAN; now my system doesn't work. Ergo, CPAN must be to blame."

* The end user -- who isn't the one who made the mistake in the first place, and isn't responsible for fixing it (assuming he/she even knows HOW) -- is the one who suffers.

I guess I just consider this an example of when the "Right" thing to do isn't necessarily the "Best" thing to do... «shrug»

Note: I'm certainly not arguing that the entire history of misfeatures has to be preserved for compatibility -- e.g. Windows -- but keeping an ecosystem robust requires at least a moderately conservative approach to mitigate unforeseen failures, methinks. (Sure, making an omelet means breaking a few eggs, but you could at least do it over the sink, rather than spilling food all over the floor...)

At any rate, keep up the good work! Personal frustrations aside[*], I heartily respect the effort and commitment you and the rest of the Perl community have invested to make the world a better place. :-D

[* - FYI, the broken method invocation came after a good day and a half of being unable to check in changes at $work; I had to reinstall SVN::Base / Alien::SVN under Mountain Lion, which wasn't working due to a number of non-universal -- i386 vs. x86_64 -- shared libraries, both in the Subversion build itself and its "libneon.dylib" dependency. Finally, after getting all the right "CFLAGS=" options figured out over there, this otherwise trivial bug popped up. Sorry if it was the proverbial 'last straw'...]