The research note goes into *much* more detail but the overview is below.
Keep in mind that this content is targetted at mainstream IT organizations.
PHP has been a cornerstone technology on the Web for more than a decade. While its adoption among mainstream IT organizations has been limited in the past, many corporate application development (AD) projects are discovering the unique benefits of PHP.
- The PHP worldwide developer count will grow to as high as 5 million developers by 2013, up from 3 million in 2007 and 4 million in 2009.
- In the short term, PHP will remain a widely adopted Web development technology.
- Over the long term, PHP will encounter increased competition from technologies such as Microsoft ASP.NET, Java, Python, Ruby, etc.
- Consider PHP for projects that require a combination open and nonproprietary technology, on which to build architecturally basic (but not necessarily small) dynamic Web applications.
- Consider PHP as a supporting technology in a broader portfolio of AD technologies, where it can provide a specialized toolset for building Web graphical user interface (GUI) front ends to service-oriented architecture (SOA) back-end services.
- Consider adopting and customizing industry-proven Web solutions (e.g., Drupal, MediaWiki, etc.) built on PHP before building solutions from scratch.
View Free, Relevant Gartner Research
Gartner's research helps you cut through the complexity and deliver the knowledge you need to make the right decisions quickly, and with confidence.Read Free Gartner Research
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.