3 ms·
I can see how this can come in handy, but setting up a LAMP server on localhost is so easy nowadays that I can't help but think this is a little redundant. Sur
by acabal 14y ago
I can see how this can come in handy, but setting up a LAMP server on localhost is so easy nowadays that I can't help but think this is a little redundant. Sure you get a full-blown Apache install but honestly, calling that bloat is semantics on anything but the worst of developer machines. I wish they had spent the manpower working on core language features instead.
- nateabele 14y agoCore language features? Oh, you mean like all these guys? http://nikic.github.com/2012/07/10/What-PHP-5-5-might-look-like.html http://nikic.github.com/2012/07/10/What-PHP-5-5-might-look-l...
- acabal 14y agoI'm not saying things aren't progressing, all I'm saying is that on any project there's a limited amount of manpower, and how you allocate that manpower is important. Personally I think there are more pressing things to allocate manpower to in PHP than a built-in web server, when Apache is already so simple to configure for serving PHP. Furthermore this kind of web server would only be useful for the most basic of projects. As soon as a person dips their toes into anything remotely complex, they're going to need their development server to mirror the production server as closely as possible, especially with things like php.ini and rewrites. So why not just set it up like that to begin with?
- robryan 14y agoIt is an open source project, I am guessing that one or more contributors decided they wanted the built in be web server. There is nothing stopping others getting involved if there were other things they want to see in future PHP versions.
- ars 14y ago> how you allocate that manpower This is open source. You don't "allocate" manpower - people work on whatever they find interesting.