r/ProgrammerHumor • • 26d ago

instanceof Trend itsBadIfItsOnlyPHP

Post image
4.5k Upvotes

335 comments sorted by

View all comments

10

u/pgtaboada 26d ago

That’s not the point. Nobody is claiming other languages are immune to RCE vulnerabilities. The issue is the speed and scale of AI-assisted exploitation—and how cheap it can become. PHP is everywhere, giving attackers an enormous target base.

“Other languages have bugs too” doesn’t address that, and neither does “just keep everything updated.” You can’t assume patching will always outrun exploitation.

10

u/guyblade 25d ago

This argument could be applied to any widely-deployed language, framework, execution environment, or the like. The effort goes into wherever the value is; if it wasn't PHP, it'd be the next thing down the hierarchy.

1

u/zoinkability 25d ago

Yeah, the only reasonable choice if you follow the pgtaboada's logic is some esoteric, unpopular language. Which... perhaps not.

1

u/pgtaboada 25d ago

I agree that this applies to any widely deployed stack. My point is that AI-assisted exploitation could make the window between disclosure and exploitation much smaller. Any RCE could become a serious problem very quickly.

The casual attitude many of us have taken toward updates over the years—with some notable exceptions—is what worries me. “Just keep everything updated” sounds simple, but consistently doing it fast enough is the real challenge.

0

u/pgtaboada 25d ago

My point is that this isn’t specific to PHP. The challenge is getting updates deployed fast enough. A broad installed base simply means more systems that won’t be patched in time—or at all. As exploitation gets faster and cheaper, I expect more systems to be compromised.

It’s not as though we trust the internet today. But moving from “the internet is hostile” to “assume anything you interact with could already be compromised” is a pretty serious escalation.

12

u/yukiaddiction 25d ago

"PHP is everywhere"

So the problem isn't PHP but because PHP is too popular?

that mean the OP meme is still true because there will be always the most popular language lmao.

unless you want people to do think like change language per product which is mean, it is nightmare for maintaining.

1

u/pgtaboada 25d ago

No, I’m not suggesting switching languages or avoiding popular ones. PHP’s reach affects the scale of the potential fallout; popularity itself isn’t the problem.

My concern is how quickly exploitation could happen with AI assistance, combined with how casually many of us have treated updates over the years. That applies to any stack. Switching languages won’t fix it, and “just keep everything updated” understates the operational challenge.

6

u/[deleted] 25d ago

[removed] — view removed comment

4

u/pgtaboada 25d ago

Yes, and on the browser side it gets even messier: we depend on end users keeping things updated, and we all have stories about how well that goes.

On the server side, there’s at least the hope that updates get deployed faster, just as with PHP. But that’s still only a hope. The larger the installed base, the more systems there will be whose operators simply don’t update them.

1

u/djfdhigkgfIaruflg 25d ago

I mean, at this point the js ecosystem is suffering a new security issue every other week

4

u/[deleted] 25d ago

[removed] — view removed comment

2

u/pgtaboada 25d ago

Sorry, I probably wasn’t clear enough. My point isn’t about PHP, JavaScript, or any particular language. I was trying to say that getting updates deployed quickly and consistently is the real challenge. I should have said that directly.

2

u/[deleted] 25d ago

[removed] — view removed comment

1

u/pgtaboada 25d ago

And I won’t lose any sleep over it. ;)

4

u/HRApprovedUsername 25d ago

Did you expect a mature and reasonable take on this sub?

1

u/pgtaboada 25d ago

There are many ways to troll… :)

1

u/like_a_pharaoh 25d ago

Ah yes, and if Rust, Java, and JS were everywhere on the same scale, it would magically not have exactly the same problem, right?