Skip to content

Announce State of PHP survey - #1996

Open
pronskiy wants to merge 1 commit into
php:masterfrom
pronskiy:state-of-php-survey
Open

Announce State of PHP survey#1996
pronskiy wants to merge 1 commit into
php:masterfrom
pronskiy:state-of-php-survey

Conversation

@pronskiy

@pronskiy pronskiy commented Aug 25, 2026

Copy link
Copy Markdown
Member

The first State of PHP survey is still open but closes soon, and php.net is about the only place it hasn't been announced. Adding it as frontpage news.

It's run by The PHP Foundation together with JetBrains PhpStorm. Aggregated results come out later this year as the State of PHP 2026 report, and the anonymized raw dataset gets published alongside it, so anyone can check the numbers or do their own analysis.

Some precedent, since there's nothing written down about what goes on the frontpage:

  • php.net has carried a survey before — the PHP Usage Survey in 2003, run and hosted by Zend, with their logo and a giveaway of 50 t-shirts. The results got a second frontpage post. This one has neither a logo nor a prize.
  • Frontpage news that isn't a release or a conference is rare but not new, inclusing two of them Foundation-related: the Foundation announcement (2021) and the core security audit (Add security audit post #1254).
  • Other ecosystems announce theirs on the official site: Rust yearly since 2016, Go on the Go blog.
  • Python does exactly this. The Python Developers Survey is run by the PSF together with JetBrains, every year since 2017, and they publish the anonymized raw data. Their methodology says responses were collected via "python.org and the PSF blog, official Python mailing lists" and that "no product, service, or vendor-related channels were used to collect responses", which is also the argument for announcing it here. It got 30k+ responses that way.

/cc @ThePHPF @ElizabethN

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants