Thursday, September 03, 2009

use Moose; or no Moose;

recently "Moose or no Moose" is spreading to the Perl world.

Moose or No Moose
Command Line Moose or Knowing what You Don't know.
Re: Moose Or No Moose
Take arms against a sea of troubles
Re: Re: Moose Or No Moose
Moose Startup Time over Time

basically I agree with Adam Kennedy that Array::Compare shouldn't based on Moose. Test::Warn is a popular module and Array::Compare without Moose can totally ease the install of the Test::Warn.

in the meantime, I would agree with Stevan Little that we shouldn't hold the usage of the Moose. it's a great module with great idea and great contributors. I use it in my daily life and it works great. once more and more people/module use Moose, the problem wouldn't become a problem.

I think Padre should use Moose, I know Adam would reject that, but I insist on that Padre will benefit from Moose even Class::XSAccessor is the fastest accessor module now. Padre will be in a better structure and much more easy to read if it's coded with Moose. Plugin/Document/Highlighter would be easily written and plugged.

another thing is that I met the problem before. Long time ago people rate down WWW::Contact because it uses Moose. but I think it's not true. Moose helps me to build the module.

at last and in short, I think simple module (like only use the accessor of Moose) shouldn't use Moose but large software/module like Padre should use Moose.

Thanks. just personal thoughts.

Labels:

7 Comments:

Blogger zhang said...

another thing is that I met the problem before. ==> another thing is the problem I met before. .... Maybe I misunderstood u.

9/05/2009 12:43 AM  
Anonymous beckheng said...

我想Moose是不错的,因为Mason之父Jon思考Mason 2.0也是使用Moose,代替现有的subroutine方式。

10/03/2009 8:36 PM  
Blogger keep something here said...

i wonder if google code upload is nolonger working anymore?

i am running it on win2003 with all necessary module installed


i got the error
"google code upload server said: 403 forbidden (403)"

what is the possible reason of it? my email is floristxp"at"gmail.com

2/27/2010 4:00 AM  
Blogger keep something here said...

i wonder if google code upload is nolonger working anymore?

i am running it on win2003 with all necessary module installed


i got the error
"google code upload server said: 403 forbidden (403)"

what is the possible reason of it?

my email is floristxp"at"gmail.com

2/27/2010 4:00 AM  
Blogger Fayland said...

hmm, I tried on my WinXP and it works fine.

E:\git>googlecode_upload TemplateExtract.pod
Please enter your project name: fayland
Please enter your googlecode.com username: fayland
** Note that this is NOT your Gmail account password! **
It is the password you use to access Subversion repositories,
and can be found here: http://code.google.com/hosting/settings
your password:
Please enter your file summary: Test
Please enter your file labels (eg: 'Featured, Type-Source, OpSys-All'):
The file was uploaded successfully.
URL: http://fayland.googlecode.com/files/TemplateExtract.pod

2/27/2010 10:51 AM  
Blogger keep something here said...

i still stucked on google code upload


i installed your module by
perl Makefile.PL
nmake
nmake test
nmake install


and it stall all necessary module for me

and i this time found my passrod from http://code.google.com/hosting/settings which i do ignored last time


and i still got error :
google code upload server said: 500 cant locate object mothod "configure" via package "net::https"


it is means there is something wrong with "net::https" ? or i did not installed this module yet?

3/15/2010 2:36 PM  
Blogger Fayland said...

can you upgrade your LWP::UserAgent?

or what's your version of LWP::UserAgent

Thanks

3/15/2010 2:57 PM  

Post a Comment

Links to this post:

Create a Link

<< Home