3 ms·
Honestly, for low end stuff, mod_php is fine. I've just spent the day beating some circa y2k perl code into submission on a modern shared hosting platform too.
by singingfish 11y ago
Honestly, for low end stuff, mod_php is fine. I've just spent the day beating some circa y2k perl code into submission on a modern shared hosting platform too. That's sort of fine too (helps that I'm an expert and know how to make debugging the PoS easy).
Wordpress is an OK product. On the other hand I reckon php is a bad technology to stake your career on. Perl less so, bear in mind it's been around for several waves of the latest greatest thing and is still going strong. Still I quite enjoy javascript sometimes, it's like a syntactically crippled perl with good vendor support. Perl6 looks cool, I hope I get the opportunity to mess with its async stuff.
- masklinn 11y ago> Honestly, for low end stuff, mod_php is fine. Then again, so's GCI.
- singingfish 11y agoYeah, but Plack::Request/Response is a better API to the same for low end stuff and will expand to bigger things as required.
- dspillett 11y agoThough all the forking of standard CGI makes it far less efficient, which is quite a concern to a cheap shared hosting provider in a saturated market: they need to cram as many accounts as possible on as few machines as possible to have any hope of not running the business at a loss. Fast_CGI helps here of course, but then you have your users needing to be able to create long lived processes which moves the problem to one of memory use and process cycling & other management.
- singingfish 11y agofwiw I'm currently working on tools to port a fastcgi perl cgi script to a more modern infrastructure, for money. I'll try and work up the fun bits into an article in due course.