Is there any plans to establish a platform change from perl cgi to a fully functional PHP version? I would think going to php would be a far better solution with more flexibility in development.
Reported on Movable Type 4.2
Is there any plans to establish a platform change from perl cgi to a fully functional PHP version? I would think going to php would be a far better solution with more flexibility in development.
Reported on Movable Type 4.2
I have asked Anil this very question, and got back a pretty good reason for "no." At least at the time ;)
Moving from Perl to PHP would introduce such a huge amount of bugs of its own. That was the gist of what he told me. It makes sense. Which would you rather have, improvements to MT or a new version of MT in PHP that has no new features?
too bad... because there is more opportunities for open source from the php side of development.
I might also mention the amount of plugins for MT that would cease to function were it re-written in php.
I've resisted this long, but seriously, Pixelwm. What exactly are you basing these claims of more opportunities and greater flexibility on?
While I suspect this is a troll...
The simple reason is that it would do nothing, except make a release that breaks everything just so that PHP fanbois can have fun.
If 6A were to rebuild in any language, it would be either Ruby or Python, as those two languages are far superior to PHP in every respect, and can go toe-to-toe with Perl on features.
Any remotely competent developer can learn enough Perl to write Movable Type plugins and extensions. The APIs are far better written than any of that crap that the PHP developers call their standard API; if you work in Java or .NET development PHP will be enough to make you want to vomit whenever you get into non-trivial work.
'fanbois'? - Who is the troll here? You're being hopelessly inflammatory.
Look at the number of patches a well written and popular PHP application has, compared to MT.
Setting up MT is not so hard, even on shared hosting. Also, one install for all your websites is a pretty awesome thing in itself, add static publishing into the mix (MT's best feature, imo) and there's no good reason to move to PHP.
While those things are all possible for a PHP application, I think the larger issue here is just "why?" If 6A were to start work on a new version, it would make sense to wait another year or two for Perl 6 and its Parrot VM to mature. Once on the Parrot VM, MT could have plugins written in any language that can be compiled down to Parrot instructions. That would mean that guys like me could use Python instead of Perl without having to use kludges ;)
Why would anyone in their right mind want to move a functioning piece of software to a different scripting language?
Because most people who think that PHP is teh c00l3st language ever and full of sweeping innovation can't learn enough Perl to write even a basic plugin for Movable Type.
Isn't it true that in MT's perl you could call outside web services written in other languages such as php or ruby?
Doesn't that make life easier than as Michele says, 'moving a functional piece of software to a different language?'
I'd be much more likely to use MT if it was all in PHP.
Sorry, 'Mike T', but Ruby and Python are in much more limited use for a variety of reasons. And Perl, is well, not worth my time to learn at this point - it's not 2002 anymore.
It would be nice if PHP developers behaved like that. They're finally getting namespaces, which means that they're finally starting to behave like a language written for the needs of the early 1990s.
do someone have plan to finish the MT to php ??
i notice the /mt-cgi-directory/php have full-feature template engine
That is for dynamic publishing functionality which has been included for a long time.. MT's backend is Perl but you can have it publish just about anything; static HTML, PHP, js, css, aspx, rb, rtf.