284
PHP Moment (lemmy.world)
all 27 comments
sorted by: hot top controversial new old
[-] Oth@lemmy.zip 94 points 1 year ago* (last edited 1 year ago)

Tell me you've never used PHP without telling me you've never used PHP.

It's known for giving a complete stack trace, it's nearest neighbours and their god damn grandkids the moment it so much as coughs up a warning. For the longest time it was notorious for doing this as the default error logging level.

I'm aware it's cool to hate on PHP, but it has plenty of things to dislike without straight-up inventing nonsense.

[-] Max_P@lemmy.max-p.me 21 points 1 year ago

Also that table would be generated by Xdebug, not PHP itself. PHP's traces are plain text by default. That said Xdebug is pretty good in itself, I've used it for a decade.

The stack traces are fine. You can even define a global handler for unhandled exceptions to log them, and it gives you an opportunity to also inspect every value of every function argument and whatnot. It's not lacking in debugging abilities that way.

If you're gonna make fun of PHP errors, at least make fun of "PHP Error: Unexpected T_PAAMAYIM_NEKUDOTAYIM on line 69".

[-] hakunawazo@lemmy.world 10 points 1 year ago* (last edited 1 year ago)

For those not in the know, the T_PAAMAYIM_NEKUDOTAYIM is just a double colon like this ::
It's a scope resolution operator for example to directly access a class constant or method without an instance.

[-] folkrav@lemmy.ca 5 points 1 year ago

This. I haven’t touched PHP since 7.1 dropped, but error messages and stack traces were pretty far down my list of complaints about the language.

[-] pixelscript@lemmy.ml 2 points 1 year ago

PHP stack traces are effectively identical to Java's in every metric I'm concerned about.

If you get them sensibly in a log file, anyway. If you allow PHP to render this god awful fugly table inline with your page? Well, have fun. Yes, all the same info is there, and on paper it's organized in an easier to read format. But oftentimes the table will collide with and mangle with other elements and styling on your page, making the trace irritating or impossible to read.

This isn't much of a problem of course, because aforementioned log file is absolutely the way to do it in the first place, and PHP lets you. And hey, absolutely obliterating your page DOM in strange and exciting ways on error sounds like a fantastic way to ensure errors get caught and addressed in testing, so even the unpredictable mangled DOM bullshit is useful in its own way.

But if someone wants to dunk on PHP for at least outwardly appearing to promote trying to debug it with these awful stack trace tables, I think that's a well-earned roasting.

[-] devfuuu@lemmy.world -1 points 1 year ago

I liked when it screamed at me some german error message out of nowehere or some other weird language. Totally sane language.

[-] tsonfeir@lemm.ee 27 points 1 year ago

So many people don’t know how to use PHP

[-] eager_eagle@lemmy.world 24 points 1 year ago

nice stack traces don't matter when PHP has the best built-in name: die()

[-] tiredofsametab@kbin.run 3 points 1 year ago

die unless qw(perl did it first);

[-] poinck@lemm.ee 17 points 1 year ago* (last edited 1 year ago)

While this is very funny, I think with PHP you can achieve error traces like in Java, nowadays. And no, I am (not) a senior PHP developer. ^^

Edit: I used PHP-4 ages ago and now I am relearning >=PHP-8. Not sure whether junior or senior.

[-] TCB13@lemmy.world 11 points 1 year ago

Only if people actually tried to learn PHP.

[-] desmosthenes@lemmy.world 9 points 1 year ago

[object Object]

[-] Semi-Hemi-Demigod@kbin.social 8 points 1 year ago

Having written PHP for many years, all I have to say about it is T_PAAMAYIM_NEKUDOTAYIM

[-] flashgnash@lemm.ee 8 points 1 year ago

Rust: Here's an explanation of what you did wrong, where you did it, and a detailed wiki page about the subject

[-] lawrence@lemmy.world 4 points 1 year ago
[-] poinck@lemm.ee 2 points 1 year ago

I salute you.

But which version?

[-] Cysioland@lemmygrad.ml 1 points 1 year ago

No, it's what XDebug does to your stacktraces if you have display errors on

[-] doomkernel@sopuli.xyz 1 points 1 year ago

Progress errors be like: "I can't understand after line 32"

Good luck finding out what

[-] Clbull@lemmy.world 0 points 1 year ago

Isn't Java known for spitting out random errors?

[-] summerof69@lemm.ee 8 points 1 year ago
this post was submitted on 28 Feb 2024
284 points (92.3% liked)

Programmer Humor

37093 readers
94 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS