Follow Slashdot blog updates by subscribing to our blog RSS feed

 


Forgot your password?
Close
typodupeerror
×

PHP Optimized for Windows Server 2008 182

Posted by Zonk from the dogs-and-cats-living-together dept.
Stony Stevenson writes "It used to be that popular PHP applications would run more poorly on Windows Server than on a Linux or Unix servers, for which PHP had been optimized. Specialist in the PHP language Zend Technologies now says that's no longer the case. The Zend Core commercially supported form of PHP has been certified by Microsoft as ready to run 'with performance and stability' on Windows Server 2008, said Andi Gutmans, co-founder and CTO of Zend. Previously, PHP 'didn't run as well as it should on Windows,' said Gutmans, despite the fact that 75% to 80% of PHP users were developing on Windows workstations."
This discussion has been archived. No new comments can be posted.

PHP Optimized for Windows Server 2008 More

PHP Optimized for Windows Server 2008

Comments Filter:

  • In Short (Score:5, Insightful)

    by TheRealMindChild ( 743925 ) on Tuesday March 04, 2008 @12:29PM (#22636724) Homepage Journal
    So, in short, they aren't using cygwin anymore to compile it.

  • FastCGI != Apache Module (Score:5, Informative)

    by Foofoobar ( 318279 ) on Tuesday March 04, 2008 @12:30PM (#22636736)
    As a CGI you still have to make extra system calls that you don't have to make as an apache module. Running under FastCGI is a good first step but it still doesn't make it as fast as running it as an Apache Module. In a recent post on Slashdot about how Microsoft is learning from open source, they claim they made IIS more modular like Apache but this is not the case as PHP proves otherwise they could run it as a module.

    I applaud the effort to embrace open source languages though and hope they continue along this path of self improvement.

    • Re: (Score:3, Interesting)

      by theGreater ( 596196 )
      Furthermore, FastCGI under IIS (haven't tried with anything newer than 2003r2/IIS6) isn't fully compatible with at least one popular application that I can think of.

      http://wordpress.org/support/topic/150672 [wordpress.org]

      -theGreater's $0.02.

    • Re:FastCGI != Apache Module (Score:5, Informative)

      by arodland ( 127775 ) on Tuesday March 04, 2008 @12:45PM (#22636944)
      In my testing (Perl, not PHP, but I don't think it particularly matters here), a "real world app" ran 98% as fast under FastCGI as under mod_perl -- and FastCGI is easier to deploy, easier to maintain, and (in the simple case) better on memory. Is it really worth chasing that extra 2%?

      Of course, in the case of PHP, there's an extra incentive. I don't trust PHP's security or sanity for shit. So I'd much rather have it running in its own process with its own permissions than have it dynamically linked directly into my webserver :)

      • Re: (Score:3, Insightful)

        by Firehed ( 942385 )
        PHP's security isn't so much a problem compared to non-security-conscious developers working with it since it's so damn easy to pick up. If you're running stuff like $query="INSERT INTO `users` (`name`) VALUES '${_GET['name']}';";, it really doesn't matter what language you're using.

        • Re: (Score:3, Funny)

          by mini me ( 132455 )
          Very true. I once inherited a Ruby on Rails project that had code similar to this:

          @variable = eval("@#{params[:variable]}")
          I think I'd rather see SQL injection vulnerabilities.

        • Re: (Score:3, Informative)

          by TheRaven64 ( 641858 )

          If you're running stuff like $query="INSERT INTO `users` (`name`) VALUES '${_GET['name']}';";, it really doesn't matter what language you're using.

          But a language which uses this kind of thing, rather than a printf analogue with encoded type information is much more likely to encourage this kind of code. The PostgreSQL C interface contains a printf-like function which doesn't include the arguments in the SQL string at all, it puts pointers to arguments and the arguments themselves in the packet sent to the server so there is no escaping ever required because string arguments never go through the SQL parser. The same is true of most databases, and ye

      • Yeah but thats mod_perl. mod_perl has been known to suck. The recommended way from Zend and Apache for PHP has always been as an apache module. Also to get alot of the added benefits like virtual hosting and stuff, you need to upgrade and the upgrade costs. For that you may as well stick with the apache module.
        • mod_perl is indeed known to suck (or at least to require a lot of tuning and babysitting), but slow it isn't. Point is, it's just not necessary (or very beneficial) to have an Apache module if the only place your app is going to run is the Request phase. If the PHP devs disagree then IMHO they don't know what they're talking about. Or it's got something to do with that product they're trying to sell you. :)
          • mod_php doesn't cost anything. Apache doesn't cost anything. FastCGI on the other hand is a product which has upgrades and a server product that costs. So it sounds more like FastCGI and Microsoft have more to sell than the Apache foundation.

            • mod_php doesn't cost anything. Apache doesn't cost anything. FastCGI on the other hand is a product which has upgrades and a server product that costs. So it sounds more like FastCGI and Microsoft have more to sell

              Er... no? FastCGI is an open protocol (not product) with scads of free implementations that's compatible with a pile of webservers. As for "having something to sell", I meant Zend, who have a big hand in PHP, and are clearly interested in selling you something.

              • PHP is a GPL language; ZEND is a company than makes products that extend the language. FastCGI is a protocol; Microsoft and other companies make products you purchase that extend that protocol. Sounds to mean that you are complaining about the same thing I am and would rather have an Apache module as well. :)

    • Re: (Score:3, Interesting)

      by pdxp ( 1213906 )
      PHP used to also ship as an ISAPI module, but it did pretty much the same thing that the CGI did- reload the interpreter for every single request. I'm not sure why they bothered with FastCGI when it would've required about the same amount of effort to write an ISAPI extension. It might have to do with the fact that PHP's source code was more spaghetti-like than any PHP code one could dream up, and not trivial to follow or modify.

      It would be interesting to compare the performance to that of Python [insert

      • Re: (Score:3, Informative)

        by jsebrech ( 525647 )
        PHP's issues with ISAPI are due to it not being thread-safe. We've tried to deploy PHP as ISAPI on windows, and things run fine until the customer starts using an application module that uses GD, or some other non-thread-safe extension, and then you get sporadic crashes that come more often as the load increases (which is obviously the worst time for a server crash).

        FastCGI's benefit is that every FastCGI handler is still a separate process, so you don't run into threading issues, while at the same time not
    • well, you could run php as isapi module on iis. I have tried it, i haven't done some performance testing. The problem with isapi is, that you have one configuration (php configuration) per server, no mixing of php4/5 per virtual host.

      This makes it a no brainer for anyting but playing with it. After finding this out we tested with fastcgi, it's nice but iis is still extremely complicated to handle and and the os is soo hungry (1gb ram for an intranet server and w2k3 is barely usable on the shell).

      finally i c
  • "with performance and stability"

    Excellent. This way, when it turns out to be false, they can always say: "We didn't mention 'good' performance.

    • Re: (Score:2)

      by Amouth ( 879122 )
      it is better than trying to figure out what MS app is lieing to you..

      right now i have an exchange box that is failing backup's.. it fails do to a check sum error.. dig further and it says it is failing check sum because of a bad sector....

      it is a VM... it is using a virtual disk... and the physical disk the virtual disk is on is fine...

      it just makes you scratch your head and ask.. what the fuck.

  • Light on details (Score:2, Insightful)

    by Anonymous Coward
    It would have been nice to know the areas that they optimized to get the performance increases. Unfortunately the article is a little light on the details.

  • Other incapatiblities (Score:3, Insightful)

    by Freexe ( 717562 ) <serrkr@tznvy.pbz> on Tuesday March 04, 2008 @12:31PM (#22636754) Homepage
    There are still many other compatibility issues between PHP on Windows and Linux that make it hard to push things from a Windows box straight to a Linux box without extra testing.

  • Misleading (Score:5, Insightful)

    by MojoRilla ( 591502 ) on Tuesday March 04, 2008 @12:32PM (#22636758)
    This is misleading.

    75% to 80% of PHP users were developing on Windows workstations.
    And how many of these applications are being deployed on Windows? Probably not that many. Windows isn't a great server operating system.

    • Comment removed (Score:5, Insightful)

      by account_deleted ( 4530225 ) on Tuesday March 04, 2008 @12:37PM (#22636840)
      Comment removed based on user account deletion

      • Re:Misleading (Score:5, Funny)

        by muszek ( 882567 ) on Tuesday March 04, 2008 @01:16PM (#22637524) Homepage
        Food? Are car analogies not good enough for you?

        • Re: (Score:3, Funny)

          by discogravy ( 455376 )
          lots of people eat in their cars, but who prepares food in their cars?

          I suppose you could make a very complex analogy about tailgate parties or something, but it really seems like too much trouble.
        • Just combine 'em...

          "Windows is like a tuna sandwich with it's bread welded shut..."

      • Those of us with limited bandwidth on our Linux servers and developing PHP on Windows workstations use something like PHPEclipse [sourceforge.net] with XAMPP [apachefriends.org] and test locally first, then upload to the remote server and do final testing and tweaking from there.

    • Re: (Score:2)

      by dave420 ( 699308 )
      It's not as bad as you make out. And with IIS7, it now makes a good web server, too.

    • Re: (Score:2, Insightful)

      by dedazo ( 737510 )

      Windows isn't a great server operating system.

      Not for PHP applications, no. Good enough for light testing, but not production.

      .NET-based applications on the other hand, work great. Server 2003 and 2008 now are great platforms for them. So when you say "isn't a great server", I expect you mean "for the language/technology I choose to work for", much as Mono-based apps are not exactly mainstream or very well tested in Apache.

    • Quite right, and this is actually the preferred scenario. If you are developing in an environment that performs more poorly than the production environment, then you won't be in for an unpleasant little surprise when your app hits the real world.

    • Re:Misleading (Score:5, Informative)

      by Santana ( 103744 ) on Tuesday March 04, 2008 @01:03PM (#22637222)

      This is misleading.

      Only if you have problems reading English. That sentence clearly speaks about development, not deployment.

      • Re: (Score:3, Insightful)

        by richlv ( 778496 )
        actually, it is misleading. it does not have any reasonable connection with the fact itself/article.
        well, unless those developers run windows 2008 server on their workstations.

      • Re: (Score:3, Insightful)

        by kripkenstein ( 913150 )

        This is misleading.

        Only if you have problems reading English. That sentence clearly speaks about development, not deployment.

        No, he was right on the mark. You are correct that the sentence clearly says development. But the point is that mentioning development in this context is misleading. It doesn't matter where code is written, it matters where the code is run, if you are talking about the performance of the code. TFA is misleading in that respect. It seems their point has an underlying assumption that development and production should be on the same OS or something like that; under that assumption the quote makes sense. It's

    • Re: (Score:2, Informative)

      by andigutmans ( 1250708 )
      That is exactly the point. There are very few Windows deployments because PHP on Windows was 2-3 times slower than on Linux and unstable before we made the said improvements in PHP and Microsoft built FastCGI support into IIS 7.
    • If you work for the military and build web-apps, you don't get a choice between the two. (And it isn't Linux.)

      Frankly, I was pleasantly surprised they even had PHP configured on their boxes at all (I thought it was only ASP at first). And a pretty up-to-date version as well.

    • Re:Misleading (Score:5, Insightful)

      by jsebrech ( 525647 ) on Tuesday March 04, 2008 @02:50PM (#22639472)
      And how many of these applications are being deployed on Windows?

      My company's PHP based software runs over 95 percent on IIS servers. We have a single customer that uses linux for their web server platform (a university). We're talking about big customers here, like Siemens and ISS (one of the world's largest cleaning firms), with dozens of servers each running our platform, all of them Windows servers.

      We've been deploying PHP on fastcgi the whole time. ISAPI has never been stable, and CGI has always been too slow.

      Tthe situation changes for non-intranet web apps. Those tend to be linux-hosted because people tend to outsource their hosting. But for in-house hosted software, most of the time you have to fall back on the existing network team, who is usually specialized in windows, so they tend to prefer windows-based web servers, even if it's just for the sake of uniformity.

    • Re: (Score:2)

      by Allador ( 537449 )
      I know this is slashdot and all ... but you could always consider reading a couple sentences after the one you quoted completely out of context.

      Previously, PHP "didn't run as well as it should on Windows," said Gutmans, despite the fact that 75% to 80% of PHP users were developing on Windows workstations. When they deployed their Windows-based applications to production, their performance was disappointing and they tended to develop on Windows and deploy under Unix or Linux. Now the three platforms should be available on a more equal footing, he said.

      The article SPECIFICALLY states that most develop on windows workstations and deploy on a unix or equiv.

      How exactly did my parent get marked insightful? By re-stating a sentence from the article in a hostile, anti-microsoft tone?

    • This is misleading.

      75% to 80% of PHP users were developing on Windows workstations.

      And how many of these applications are being deployed on Windows? Probably not that many. Windows isn't a great server operating system.

      Not just that, but too many developers need to at least do a portion of their work on a Windows machine (virtual or "real"), simply because no matter how compatible the stuff the server sends, IE displays things just a little different (depending on version, sub-version, fonts installed, how IE decides it wants to handle font request, day of the week...). I run a Windows box (well, two if you count the virtual session on my non-Windows machine)... I don't do my development on it - but I do use it regularl

  • Nothing to do with optimization (Score:5, Interesting)

    by dedazo ( 737510 ) on Tuesday March 04, 2008 @12:34PM (#22636778) Journal
    PHP on IIS5/6 had to run as a CGI application, because their ISAPI handler implementation was historically crappy and unstable under load. CGI under the thread-oriented (as opposed to process-oriented in *nix) pipelining model of Windows was usually not a good performer. IIS7 introduced FastCGI, which is what Zend used to "certify" PHP to run on Server 2008. But FastCGI is not an optimization, it's a new execution mode for IIS. Nor was PHP modified (AFAIK) in any way to run effectively on FastCGI. Python apps also run very well on it (which personally is more exciting to me than PHP).

    • Re: (Score:2)

      by TheLink ( 130905 )
      I like FastCGI because it's cleaner than stuff like mod_perl (and seems more robust too).

      It's like CGI in that you can write FastCGI apps in all sorts of different languages, and they are more portable across different webservers (if they support fastcgi and you can figure out how to turn it on).

      Years ago I tested my FastCGI perl apps which were on Apache on a Zeus webserver and they worked fine (can't recall if they worked faster, they might have :) ). Unless Microsoft has been naughty again, they'd probab
    • PHP on IIS5/6 had to run as a CGI application... IIS7 introduced FastCGI...

      Not true. For years there's been an unofficial FastCGI library for IIS (by Shane Caraveo), that you could use with PHP4 and PHP5. We've been deploying on windows using this library, and it ran stable and at acceptable performance levels.

      The new microsoft FastCGI library is simply an officially supported form of FastCGI. It ships with IIS7 by default, and is available as an add-on install for IIS6. It works fine with PHP4 and PHP5, bu

  • Marketing (Score:3, Interesting)

    by LingNoi ( 1066278 ) on Tuesday March 04, 2008 @12:35PM (#22636810)
    Meh, I wouldn't believe Zend. They're in corporation with Microsoft to provide better interoperability... They're not going to go into a deal with Microsoft and then say, "Still sucks on Windows server" are they?

    Surely it should also run better on all windows servers so why just 2008? Unless they're trying to find reasons for you to upgrade..
  • "despite the fact that 75% to 80% of PHP users were developing on Windows workstations."

    I do not know many people using Windows Server as a workstation...

    • Re: (Score:2, Interesting)

      by jfbilodeau ( 931293 )
      You mean there's a difference between Windows as a workstation and Windows as a server beyond price? Oh, and the crippling of a couple of services?

      Maybe I should become one of the 75% to 80% of PHP developers who use this 'Windows' thing and see the difference myself.

    • Re: (Score:2)

      by Allador ( 537449 )
      What does your post have to do with the sentence you quoted? I see no relevance.

      The sentence you quoted says that the majority of PHP developers develop on a windows workstation, and then the sentence after the one you quoted says that most of these then deploy to a unix or linux.

      Given that, what does your response: "I do not know many people using Windows Server as a workstation..." have to do with anything?
    • I'm running Server 2008 x64 on my desktop. I'm developing against IIS7, but I won't be writing PHP in the near (or far) future tyvm.
  • Go on. You know you want to do it.

  • PHP on Windows (Score:5, Insightful)

    by corychristison ( 951993 ) on Tuesday March 04, 2008 @12:42PM (#22636906)
    ... like Ruby on Rails?

    Just kidding. Seriously, though, it said "commercially supported form of PHP". Be sure to take a big mental note of that.
    Commercial == fee's. Based on Zends track record of charging for things, it's not going to be cheap for single developers... I have a feeling it'll be in the area of $800-$1500 per CPU or something silly like that [zend.com]... in which case, why not just use a UNIX/derivative?

    • If you have to contact sales to find out the price (Score:5, Informative)

      by symbolset ( 646467 ) on Tuesday March 04, 2008 @12:55PM (#22637102) Journal

      Then the answer is: "More than it's worth."

      • Php guru: you need a windows zend license.
        Boss: So if we pay somebody else it will work better in windows
        Php guru: yes
        Boss: Windows has great tco doesnt it.

    • RoR doesn't sound as cool as PoW. They'll have to come up with a kooler phonetic acronym if they don't want to loose too many developers. ;)

    • Re: (Score:2)

      by Shados ( 741919 )
      Actually, the main thing that makes what the article states possible is FastCGI for IIS 7 and Windows Server 2008 (though there is one decent version for WinServer2003 I beleive). Its just that Zend made a version of PHP that got certified for that version of FastCGI.

      If you get any relatively tested "CGI-compliant" environment and use it with that new FastCGI version, it should run just as well. Not just Zend's PHP, and heck, not just PHP at all, it will work with the others too.
    • Seriously, though, it said "commercially supported form of PHP". Be sure to take a big mental note of that.
      Commercial == fee's.

      Zend Core is free. Zend Core in essence is what a linux distro is to the linux kernel. It provides a certified single-installer toolchain (web server + php + db layer + zend framework).

      What you can buy from them is a support package for Zend Core, to help you with installation, updating and bug resolving. Being able to pay someone else to deal with PHP performance and reliability is
    • Commercial == fee's. Based on Zends track record of charging for things, it's not going to be cheap for single developers... I have a feeling it'll be in the area of $800-$1500 per CPU or something silly like that [zend.com]... in which case, why not just use a UNIX/derivative?

      Look, if you need silly density you can pay for Solaris licenses. If licensing fees matter to you, you run Linux/BSD. If licensing fees don't matter to you, you run Windows, if you like Windows. If you can afford licensing fees and
      • The entire point of my post was to point out that they had said "The Zend Core commercially supported form of PHP" which brought me to decide to comment on it, as well as point out their obscure pricing practices for other products. "Per CPU"? Who the fuck charges like that? ... that and this was like 14 hours before you decided to comment. It's done, it's over, go home everybody!
        • "Per CPU"? Who the fuck charges like that?

          Commercial vendors. It's stupid, but people pay it.

          ... that and this was like 14 hours before you decided to comment. It's done, it's over, go home everybody!

          ADD much?

  • Why not Apache? (Score:5, Insightful)

    by edmicman ( 830206 ) on Tuesday March 04, 2008 @12:47PM (#22636974) Homepage Journal
    We run a .NET shop here, but even I wonder, why not just install Apache on Windows? Errrrr, or why not just go the easy route and put up an Ubuntu LAMP server? Everything I work on is in Windows, but I just don't see the benefit of running PHP on Windows...what does [Microsoft say] the Windows platform offers for PHP that running it on freely available platforms doesn't?
    • It's not what PHP has to offer that MS wants. They are hoping to migrate OSS developers to the Windows platform.

      Sorry, but as for me, you won't see my LAMP become a WAMP anytime soon.

      • Re:Why not Apache? (Score:5, Funny)

        by RipSUp ( 987194 ) on Tuesday March 04, 2008 @01:11PM (#22637398)
        They don't want your LAMP to become a WAMP, they want it to become a WIMP (Windows/IIS/MSSQL/PHP)

        • Re: (Score:3, Interesting)

          by jfbilodeau ( 931293 )
          Agreed.

          In 2004-05, I wrote a PHP application for a client. We had agreed ahead of time that the app would be written in PHP. Upon delivery, everything worked great on the test (WIMP) server that I set up myself. When the technician was called in to put the application in production, he said no problem. I should point out that the fellow is a hard-core and experienced MCSE.

          A month later, the application was not installed. I called the technician to find out what was happening, and I was given the story of be
        • Actually MS would prefer you to use ASP.net

      • Re:Why not Apache? (Score:4, Funny)

        by jjrockman ( 802957 ) on Tuesday March 04, 2008 @01:11PM (#22637400) Homepage
        Don't you mean Windows IIS MySQL PHP/Perl? Or, WIMP for short.

        • Re: (Score:3, Informative)

          by Phroggy ( 441 )

          Don't you mean Windows IIS MySQL PHP/Perl? Or, WIMP for short.
          Not quite - MSSQL, not MySQL!
      • And for Zend, it opens up shops that are exclusively IIS and might have banned PHP in the past for performance reasons.

    • Re: (Score:2)

      by Rakishi ( 759894 )
      If they install apache then MS can't try to lock them into using windows for the server, duh.
    • Maybe it has something to do with the fact that there have only been 3 non-critical security flaws found in IIS in the last 5 years, while Apache has had how many?

    • Re: (Score:2)

      by Shados ( 741919 )
      Because if you have a Windows domain fully configured in a large corporation, integrating IIS with all that is a snap. Actually, it most likely -already- is: Reporting Services, Sharepoint, Exchange, they all use it.

      So my question is: Why use 2 web servers when you can use only one, especially one thats already installed and locked down?

    • I just don't see the benefit of running PHP on Windows...what does [Microsoft say] the Windows platform offers for PHP that running it on freely available platforms doesn't?

      On the IIS 7.0 platform, Microsoft offers LOTS to PHP (and Perl, Python, et al), chiefly though the integrated pipeline, which will allow you to do some very interesting things like build PHP pages and apps that make use of ASP.NET's Membership and Role APIs (or the Session or Application objects, for that matter). I don't know how many people will actually be writing "extensions" to PHP in C#, but it will be possible with IIS 7.

    • Re: (Score:2)

      by chill ( 34294 )
      Not if you speak the Queen's English, it isn't. Spelling it with a "Z" is American.

      • Re: (Score:1, Offtopic)

        by DarkSarin ( 651985 )
        Actually, wouldn't that be more a case of writing the Queen's English?

        Honestly, though, I've always liked the British spelling of a lot of words as opposed to the Americanized version that I've grown up with. I seems classier in most instances.
        • Classier? The only advantage of English English is that wordplay, puns and so on are easier because we generally include more variations on words (for example a computer runs programs but a television shows programmes).

          But the rules are far stricter if you intend on writing for an audience that expect correctness (I don't write correctly for slashdot). Frankly, there are many more small rules than are really worth observing, such as past participles (learnt and earnt), split infinitives (never allowed

          • Re: (Score:2)

            by Phroggy ( 441 )

            more complicated apostrophe use (possessives ending in s always send me to a style guide)
            Just because Americans rarely follow our own rules doesn't mean we don't have them. Possessives ending in "s" get the apostrophe at the end. The big exception is "its" which is possessive with no apostrophe (as opposed to "it's" which is always a contraction).

            • Re: (Score:3, Informative)

              by Cal Paterson ( 881180 ) *
              I didn't mean to say American English has no rules. Only that English English has more, and that they are less logical and harder to remember. You're picking a grammar fight when I don't have Fowler's to hand, but from memory;

              Singular with an s-ending takes word+'s
              Plural without an s-ending takes word+'s
              Plural with an s-ending takes word+es'
              The United Nations (and other singular entities with plural names) takes word+'s

              Between this and contraction forms, it's pretty obvious why apostrophes are dyin
  • If it "didn't run as well as it should on Windows"
    .. and now it DOES
    but windows doesn't run as well as it did BEFORE ...
    doesn't that mean that we're just back to square one?

  • Hmm (Score:2, Flamebait)

    by Vexorian ( 959249 )
    Here's an idea: try making slashvertisements less obvious.
  • We do most all php app development on Windows but we use Linux for our web servers...a good chunk of folks known to me do the same - development on W and run on L. Frankly, I'm yet to come across anyone in my acquaintances who runs the programs online on Windows servers...but then I and most folks known to me run bootstrapped companies with little money (VCs yet to smile on us)...
  • "75% to 80% of PHP users were developing on Windows"

    -- But how many of those scripts are being served from windows servers? I strongly suspect far less.

  • Anybody think the real agenda here is for Zend to better monetize PHP? I don't know the numbers but my working assumptions are: some big % of web sites use PHP, the vast majority of them are not doing it on Windows, & the vast majority aren't paying Zend anything nor are they going to be receptive to any sort of costs being imposed on them.

    On the other hand, if there's a market segment used to paying somebody for their software, and paying every year to keep it running, wouldn't that be a great market

    • Re:another prese (Score:4, Informative)

      by PHPfanboy ( 841183 ) on Tuesday March 04, 2008 @05:50PM (#22642618)
      Zend is the PHP Company. I don't think it's any great secret that their aim is to monetize PHP. I'm not sure there's anything inherently wrong with that. Plenty of other companies and individuals monetize PHP by providing software, consulting, hosting and other services around PHP If there's value-add provided, companies will pay.

      You're probably perfectly aware that there are a large section of Linux using shops who are perfectly happy to pay, hence the success of RHEL and to a lesser extent SuSE and now Ubuntu all of which offer support around free stuff.

      The fact that Zend has worked with IBM on PHP for i5 (AS400) and with Microsoft for decent PHP on Windows only increases the choice of platforms PHP developers have to deploy on, makes PHP projects more popular across other user bases and means that PHP developers have a wider range of employment opportunities available to them. I don't think anyone is under the illusion that the future of PHP development is at 6 person consultancies who specialize in tweaking free CMSs, surviving on that free good stuff and creating pure karma (with no disrespect to small web consultancies intended, but it's a limited niche to attract new active members to the community).

      If you'd like to spend your time pitching PHP as a strategic application development option to Fortune 500 companies, government departments and other enterprises, I'm sure we'd all be delighted, but there's not much chance of you spending your time doing that, nor quite frankly of those entities listening to you. They do however talk to Zend.

      Zend isn't imposing a cost/tax on anybody or demanding that people pay homage/tribute, especially as PHP is a community project and not owned by Zend. During the past 2 years Zend has increased the amount of free and open source work they've done (Zend Framework and the Eclipse-based PDT) so it's not like they take and don't give.

      If there is value companies can get from Zend's solution set, then they will pay for it. And they do. It's simple cost-benefit equations. WRT your "siphoning off revenue" if you look at all the companies in the Open Source space (including MySQL, EZ Publish, Acquia and other) they all provide value adds.

      And yeah, I work for Zend. And no, you don't have to buy our stuff (but at least come check it out). And no the decision to monetize PHP wasn't made by executives on the fringe of the FOSS world, but rather technology people in the middle of it. (I have no idea whether they have hair up their asses like you claim - but can gladly inform you that that's not a sound basis for a business strategy unless you're a barber looking for a niche....)

    • Re: (Score:2)

      by Allador ( 537449 )

      Anybody think the real agenda here is for Zend to better monetize PHP?

      You do know that Zend PHP Core is free, right? You can pay Zend money if you want, but its only for support.

      There is also Zend Framework, which is a big set of value-added packaging and large-deploy/enterprise features. That costs, but you're paying for the integrated packaging and support, not that you cant do those features any other way for free.

      They've actually struck a good balance, I think.

  • Optimized double misery (Score:4, Funny)

    by 200_success ( 623160 ) on Tuesday March 04, 2008 @03:45PM (#22640544)
    PHP and Windows? They each suck enough on their own.

Slashdot Top Deals

He has not acquired a fortune; the fortune has acquired him. -- Bion

Close