Reference Appendices

PHP Adoption History: Facebook And Major Platforms

PHP grew with the public web because it made server-rendered pages easy to deploy, fit common hosting, and let teams move from HTML into dynamic applications incrementally. Its history includes personal sites and small businesses, but also some of the web's largest publishing and social platforms.

Historical examples need dates and scope. A company may begin with PHP, build custom runtimes, introduce related languages, split systems across many technologies, or replace parts of its stack. "Built with PHP" is often true for an important period without describing every current service.

Facebook's Early PHP Choice

Facebook launched in 2004 as a PHP web application. PHP supported rapid product iteration and matched the server-rendered web development model of the period.

As Facebook's users, codebase, and infrastructure grew, repeated PHP execution became a major computing cost. Instead of immediately rewriting the entire product in another application language, Facebook invested in changing how its PHP-family code ran.

This is the important engineering lesson: a successful product rarely scales through one language choice alone. Caching, databases, service boundaries, deployment systems, observability, capacity planning, and runtime work all matter.

HipHop For PHP

In 2010 Facebook announced HipHop for PHP, later commonly called HPHPc. It translated PHP source into C++ and compiled it for production. The goal was to preserve much of PHP's development speed while reducing the server resources required to execute Facebook's large codebase.

Compilation improved production efficiency but created a slower edit-and-deploy cycle and required separate development tooling. It also could not provide a perfect implementation of every dynamic PHP behavior.

The investment shows both sides of PHP adoption at unusual scale: PHP enabled rapid growth, while Facebook's workload justified specialized runtime engineering that ordinary applications did not need.

HHVM

Facebook then developed the HipHop Virtual Machine, or HHVM, using interpretation and just-in-time compilation rather than compiling the whole application to C++ ahead of deployment.

A November 29, 2012 Facebook engineering report described a massive PHP codebase, production work to replace HPHPc with HHVM, and the goal of unifying development and production execution. It also reported that HHVM had already been used in developer environments.

HHVM was open sourced and, for a period, pursued compatibility with common PHP applications. Its existence influenced wider interest in PHP runtime performance and just-in-time compilation.

From PHP Toward Hack

Facebook introduced Hack in 2014 as a language for HHVM with gradual typing and close PHP ancestry. Existing code could be migrated incrementally rather than replaced in one rewrite.

Over time, Hack and HHVM diverged from standard PHP. That means two statements can both be true:

  • Facebook's early product and enormous web codebase were built through PHP
  • later Facebook server development used a specialized PHP-derived language and runtime rather than an ordinary current PHP deployment

Do not use Facebook history to claim that present-day facebook.com is simply a conventional PHP application. Use it to understand how a PHP codebase helped a product grow and how one company evolved its runtime and language under exceptional constraints.

WordPress

WordPress began in 2003 and remains a PHP-based publishing system. Its official requirements identify PHP as the server-side language that powers WordPress.

Its significance is different from one centrally operated website. WordPress is installed across many independent hosts, organizations, agencies, publishers, shops, and personal sites. That distribution helped make PHP version compatibility, shared hosting, extension availability, themes, plugins, and long support tails major ecosystem concerns.

WordPress demonstrates PHP's reach through reusable open-source software rather than one company's private application stack.

Wikipedia And MediaWiki

Wikipedia runs on MediaWiki, the open-source wiki software developed for Wikimedia projects. MediaWiki's official documentation describes it as using PHP to process and display database-backed content and as software designed for high-traffic sites.

This is a useful distinction:

  • Wikipedia is the public encyclopedia and hosted service
  • Wikimedia is the movement and organization family
  • MediaWiki is the PHP software powering Wikipedia and many other wikis

Saying "Wikipedia uses PHP" is reasonable at the application-platform level, but the complete production system also includes databases, caches, search, proxies, queues, analytics, and services in other languages.

Drupal And Other PHP Platforms

Drupal began in 2001 and developed into a PHP content-management framework used for complex publishing and organizational sites. Its current project requirements continue to define supported PHP versions and extensions.

Other influential PHP systems include ecommerce platforms, forum software, learning systems, and frameworks such as Symfony and Laravel. Their impact comes not only from their own installations but from packages, conventions, jobs, hosting products, and developer communities built around them.

A list of logos is weaker evidence than a maintained project's source repository, runtime requirements, architecture documentation, or engineering report.

Why PHP Spread

Several conditions reinforced adoption:

  • dynamic pages could be introduced alongside HTML
  • low-cost hosting commonly supported PHP and databases
  • deployment often required copying files rather than owning a custom server platform
  • documentation and community examples were abundant
  • open-source applications could be installed and extended
  • the language evolved while retaining substantial compatibility
  • Composer later improved package distribution and dependency management
  • frameworks offered more structure for larger applications

Some of these advantages also created long-lived legacy installations and inconsistent deployment practices. Wide adoption is not the same as uniformly modern engineering.

What Large Examples Prove

Large PHP systems prove that the language can participate in serious production architectures. They do not prove that every PHP design scales automatically or that a small project should copy a global platform's custom infrastructure.

The transferable lessons are more practical:

  • profile before replacing technology
  • evolve systems incrementally where possible
  • invest in tests and static analysis as a codebase grows
  • separate application concerns and operational bottlenecks
  • upgrade supported runtimes and dependencies deliberately
  • describe historical technology claims with dates and boundaries

Evaluate Technology Claims

When somebody says a major company "uses PHP," ask:

  1. During which years?
  2. For which product or service?
  3. Is the code standard PHP, a fork, or a related language?
  4. Is PHP serving requests, powering a packaged application, or only used in one subsystem?
  5. Is the evidence an official engineering source, current requirements, source code, or an undated marketing list?

This prevents both exaggerated advocacy and exaggerated dismissal.

Primary Source Trail

Read dates and context on each source. Current requirement pages establish continued PHP dependence for those projects; the Meta engineering article establishes a specific historical state, not a timeless description of every Meta system.

What To Remember

Facebook's early PHP application grew into a massive codebase that motivated HipHop, HHVM, and later Hack. WordPress, MediaWiki/Wikipedia, and Drupal show other forms of PHP adoption through publishing and reusable platforms. Use these examples as dated architecture history, not as shortcuts for judging a language or claiming a company's entire current stack.

Before moving on, make sure you can explain why "Facebook was built with PHP" is historically meaningful but technically incomplete.

Practice

Task: Audit PHP Adoption Claims

For each claim, label it accurate, misleading, or unsupported as written. Rewrite every misleading or unsupported claim into a statement that could be defended with a primary source.

  1. "Facebook was built with PHP, so every part of Meta still runs standard PHP today."
  2. "A 2012 Facebook engineering article described a massive PHP codebase and work to move production from HPHPc toward HHVM."
  3. "Wikipedia's application platform uses MediaWiki, and MediaWiki's own documentation says it uses PHP."
  4. "WordPress lists PHP as a server requirement, so every WordPress site has the same architecture and current PHP version."
  5. "A logo on an undated technology-list website proves a company currently uses PHP for its main product."

For each rewritten claim, name the date, product boundary, and primary evidence you would record.

Show solution

Claim Review

  1. Misleading. Rewrite: "Facebook launched as a PHP web application and later developed HipHop, HHVM, and Hack as its scale and engineering needs changed." Record the period, the facebook.com web application boundary, and dated Facebook or Meta engineering sources. Do not infer Meta's entire current stack.
  2. Accurate. The claim is dated, scoped, and matches Meta's November 29, 2012 HHVM report. Preserve the article URL and publication date.
  3. Accurate. Record that the claim concerns Wikipedia's MediaWiki application platform, then cite MediaWiki's maintained manual. Do not imply that every infrastructure component is PHP.
  4. Misleading. Rewrite: "WordPress requires PHP on the server, while individual installations can use different supported versions, hosting layers, databases, caches, plugins, and deployment architectures." Record the access date and official requirements page.
  5. Unsupported. Rewrite using a named primary source: "Drupal's maintained PHP requirements page lists the PHP versions and extensions supported by current Drupal release lines." Record the Drupal application boundary, the page's access date, and the exact release table consulted. This supports a claim about Drupal's documented runtime requirements, not an unrelated company's current production architecture. A third-party logo list is only a lead.

The stronger versions avoid turning one application layer, historical period, or packaged platform into a claim about every system operated by an organization.