r/ProgrammerHumor • u/soap94 • 3d ago

Meme ancientTools

Post image
5.8k Upvotes

96% Upvoted

387 comments sorted by

View all comments

13

u/-Nastyenka 3d ago

How it feels to use Php in 2026:

Undeniably a joke, do not slime me

24

u/Hottage 3d ago

PHP before 7 was a disgusting mess..

Around 7 they started trying to mature the language with features like compiler enforced type safety and bringing other tools previously relegated to PHPdoc into the language.

PHP 8 is a decent system and features like Generators, Attributes, Fibers and first class callables have bought it near parity with other server ecosystems like .NET.

The biggest thing PHP still lacks is first-class generics for proper, type safe repository patterns.

I've been a PHP developer for over 15 years. I fucking hated 4 and 5, tolerated 7 and actually quite enjoy 8.

The biggest issue nowadays is that, for backward compatibility, a lot of the good features like type hinting are just recommended instead of enforced, so you can get situations like in Typescript where lazy developers just have everything return mixed or any.

0

u/ClamPaste 2d ago

PHP would be great if it wasn't for all the legacy code and echo "<div></div>" in views.

1

u/ArjixGamer 2d ago

I hate PHP from the bottom of my soul, but what you said is just user-choice.

I always do ob_start and ob_flush_clean or whatever the function names were.

That allows me to use normal html w/o it being in strings.

Edit: e.g.

```php <?php

function renderEmail(): string { ob_start(); ?> <html> <body> <h1>Hello!</h1> <p>This is your email.</p> </body> </html> <?php return ob_get_clean(); } ```

1

u/ClamPaste 2d ago

Like I said, legacy code. We have a huge codebase and I'm converting it when I get time. User-choice encapsulates choices made 10 years ago.

2

u/ArjixGamer 2d ago

True dat

1

u/ClamPaste 2d ago

I guess they didn't really have coding standards. I took over and I'm enforcing some things now. I should probably write them down at some point...

0

u/Hottage 2d ago

If you're gonna raw dog the HTML, just extract it into purpose built template files and return the result of file_get_contents().

1

u/ArjixGamer 2d ago

That only works if the html is static and I don't need to render content using for loops and stuff.

The alternative is using a templating language, but like, PHP is a templating language in the first place.

I always used to say "PHP is a glorified string builder"

0

u/Hottage 2d ago

If you need to render dynamic content, use a templating engine, or at least phtml files.

😭

2

u/ArjixGamer 2d ago

Yeah, let me add an entire fucking library for my WordPress plugin that only needs to render content in 3 places on the admin dashboard.

Such a dumb take to assume there is no nuance and that there is an absolute objectively better way of doing smth.

1

u/Hottage 2d ago

Doesn't WordPress already come with a massive templating engine built in, like thats it's primary purpose?

At the end of the day, if you're building a little tool for yourself that noone else has to maintain, go ham it's your code.

If you submitted that as a pull request to my clients webshop code base, it would be receiving some... feedback.

1

u/ArjixGamer 2d ago

No? WordPress' primary purpose is extensibility via hooks.

Also, WordPress was just one example.

1

u/ClamPaste 2d ago

PHP is the templating engine. Why load a separate library for that?