use Perl

I would like to add few more packages to this list, these are some of the newer package that seem attractive

4. KiokuDB
5. Reaction

They are most likely not in popular use, but they are the most blogged about

Well, few things I would like to mention here
First 25$ a year is not much (The premium account is 40$ a a year but the difference is not that big anyway, so you may save the extra 15$)

And apparently Dreamwidth seems to be trying to create or attract a community of serious bloggers who are willing to pay for their services.

So anyway, if you are serious about blogging 25$ doesn't seem that much. And its what will keep them floating!

Although thinking about a bit more, if you are a serious blogger, you should probably host your own blog to make money by allowing Google to post Ads to your site

But again 25$ isn't much if you liked what Dreamwidth is offering

what are the benefits of this 4th era windows Perl technology ( Perl::Dist::Wix )?

1. swine flu pandemic
2. a new release of strawberry Perl
3. Perl 6

okay, I am not sure why making sure that value always returns something suitable for addition is a big deal.

first of all, you should not try to modify value directly, you should ask $think to modify value for you

second if $thing know how to perform addition on value, $thing will comply

there are so many ways to know if $thing can perform addition on value

1. ask $thing if he is of a certain type
2. ask $thing if one of his ancestors is of a certain type
3. according to your liskov, ask $thing if one of his derivatives is of a certain type
4. duck typing, ask thing to perform the addition, if $thing knows how, $thing will return the addition value, else raise an error (or do nothing)
5. ask $thing if he can add stuff regardless of his, his ancestors or hi derivatives types.

The problem i see with duck typing, is making sure that thing is always in a consistent state, that no request can validate things state, when an error is raise thing should make sure to return to a consistent state, thats all!

isn't this the problem that dynamic or duck typing solves!

where you declare a method you don't say what type you want to go in. the documentation though would have the attributes needed from the object to perform the task or work asked to it by the method

Ocaml, I believe have a way to declare the attributes the objects needs to have regardless of his class or type, so i think they are half way between static and dynamic sub-classing in my opinion should be only used as a purely technical method to share code, not define types, natures or attributes!

it would be nice if you can share more details about what those MySql queries did
i cant imagine how you can drop your processing time from 7200 minutes to 10 minutes, just by using C++
i doubt C++ have much to do with the speed increase, for example, how does the same algorithm perform in Perl!

anyway, would you share more details?

I am sure it would have helped sell more copies!

Well, if it works for you today, use. If it stops working for you in the future, don't use.

If everyone worried so much about what CPAN library will still be in active development 5 years from now, now one would be moving forward and we will all stand still.

You need to be a fast learner and dynamic, learn new things as they come.

I know that you are thiking that what ever you are building now, you would still need to extend year from now, but think about it this way.

Which will live longer, your code or Moose? Isn't possible that 5 years from you would be rewriting your application is say Perl 6.2!

Anyway, don't look too far into the future, definitely don't try to predict it.

If i want to quickly evaluate a Perl expression, I open scite, set the file language to perl.

write code, hit F5 this is working great for me.

for browsing perldoc, I prefer to use EPIC.

of course if you can create a tool that combine the two, and have can run in terminal emunlators or dos, this would be great, this will be great.

i think one can easily an emacs or vim mode to do this, but a didicate simple program is welcomed

how are callbacks different from first class functions?
or are they exactly the same thing?

Well I finally " 'Padre' installed successfully ". I installed it using Strawberry Perl on a Windows XP Professional machine.

At first I was facing problems installing Padre (and several other modules), but all now installs fine after I delete everything in my build folder( C:\Documents and Settings\tclwarrior\Application Data\.cpanplus\5.10.0\build ) before installing any module that fails.

The connection is obvious. Moose is optimized (or optimizes Perl5) for Object Oriented Programming.

So by using Moose you overcome the problem you talked about in your post: that Perl5 by default is not optimized of OOP.

And I would like to highlight one important characteristic of Perl, Perl is supposed to make things easy: Easy things -> Trivial, Hard Things -> Easy and Very Hards Things -> Reasonably hard.

Printing hellow world, is easy, therefore should be trivial. Java doesn't make it trivial!

OOP is hard, or I would say very Hard. Perl via Moose makes it reasonably hard.
And compared to what Moose have to offer, I would say, Java doesn't make OOP any less harder!

Finally, Perl is a different game than Java, I like what people were able to build using Java, but I like Perl for what it make possible for me to build!

Well, the benefit of interfaces I think it that it should save you time, collecting the list of methods you need to implement in you mock object.

In a statically typed language, you will just read the interface. And you are sure this is only what you need to implement, else the application would not compile

In a dynamically typed language, you will either have to filter the code that use the object you want to mock to see what is bein used, a process of trial and error. Or you will rely on documentation, which is not as strong as a compile time check.

So the lesson I learned is, programming with interfaces helps in creating mock objects.

And the main problem I see is figuring out what to implement or override, not how?