Good Time

Virtonomics :: Economic online game
The main goal in “Virtonomics” is to create a successful business. Players take control of a small business enterprise with aspirations to expand their business by going i…

Why? Because PHP is perfect for somethings whereas Melody’s templating language will not be.

To be 100%, absolutely clear: I do not code a single line of Perl when building a web site with Melody and Movable Type. Perl is exclusively for the domain of the core application – not the web sites it publishes.

For a lot of us, Wordpress does just fine.

Then you are fully encouraged to continue using it. MT developers have even been known to occasionally recommend WordPress, based upon people’s needs. It’s shocking, I know.

I’m not sure why you seem convinced this is a contest, but it’s not due to anything we’ve said.

I have no particular plans to lure anybody anywhere. There are enough fundamental differences between WordPress and Melody/MT that I personally think it’s up to the user to weigh the options. We’ll post features and such when they’re solidified, and everybody can make their own decision.

How do you plan to lure bloggers from Wordpress to Melody? Not all of us are willing to put 10 hours to learn a new blogging platform.

It’s much less forgiving than PHP and – for better or for worse – it has a smaller set of built-in functions and fewer available frameworks. When someone’s learning a new scripting language, though, it’s very seldom going to be perl.

I would really like to see a way to bring some of the settings to the actual sight (within the theme). Especially when a user makes a lot of comments, they need a place to keep track of their activity on the site.

Perl is a fine language, but I think people are more familiar with PHP, especially for blogging/CMS platforms.

That is why work on a new installer for Melody has already begun!

As for what Melody might do that Drupal can’t? Oy. Too big a question to ask in a forum if you want particulars. Drupal is a lot like Perl, 16 different ways to do things and maybe one is super efficient.

In fact, the developers could do themselves a huge favor by reworking the install process.

What we hope to achieve with Melody is expand its developer base — no one is more aware of the challenges presented to us in that respect than I. That is why increasingly you will see the platform evolve to minimize and even eliminate the reliance on Perl to build plugins and themes. A good example of this is the Config Assistant framework I built which I hope makes its way into Melody in the first release.

In the end what matters most is whether the product is solid, if it is fun to use, if it is secure, and if people like to use it.