Yeah, why?

I know it's popular to bitch on php but I've found it's all for the wrong reasons. The vast majority of the internet still runs on it and it's a breeze to work with, I love it. It's safe, it's fast, it's great.

I've worked with a variety of JavaScript frameworks and they all give me headaches.

If the method does a long thing, the keep it long. I do a lot of data analysis and simulation, and so often people who came before had this urge to shorten methods, so we get:

def do_calculation(N, X, y, z, a, b, c):
    # Setup stuff
    for i in range(N):
        calclation(X[i], y, z, a, b, c)`

Sometimes there's a place for that, like if calculation could be swapped for a different function, or if calculation is used all over the program. It's a pretty good clue that something is up though when the signatures are almost identical. Of course, that has just led to people writing:

def do_calculation(big_struct):
    read_data(big_struct)
    calculate(big_struct)
    write_data(big_struct)

There are various exceptions where up to 200 lines is still okay, yes. The 50 lines rule is more a good rule of thumb.

From what I've seen is that 99% of the PHP hate is people parroting slogans others came up with, and the rest is that there are inconsistencies with the function signatures.

That last part is very true, of course, but not really an issue with modern editors as they will already tell you what's expected. On the other hand, the inconsistencies are still there for a reason: compatibility. JavaScript what's a nightmare to work with because every week an update would break shit because of changing method signatures in JavaScript packages. PHP always worked and remained working because it changed so little in that respect.

In all other areas it hugely improved and matured over the years, just like all programming languages.

So yeah, I find the PHP hate childish, really.

I know that there are loads of solutions out there that can do this for you, though I don't have much experience with it myself directly. Not a great fan of docker, still, as it's not a requirement and in many cases that extra piece that fails and then is a PITA to fix.

I'll look to include it in my own framework, though

Those benefits both make sense, but are those really the original motivation for Microsoft designing the Blue Screen of Death this way? They sound more like retroactive justifications, especially since BSODs were around well before security and internationalization were common concerns.

Not when it's my own computer. My computer needs to give me useful messages.If it's a website then the site MUST log correctly in the log files...

If it's a translation issue then just use English, everyone that can understand logs can (or at least should) understand that