[No PHPun Intended] "I code in PHP"
-
"This can't be true because PHP is dead."
-
"This can't be true because PHP is dead."
That is not dead which can eternal lie.
Though HP's disturbed mind couldn't ever come up with something as upsetting as the average PHP application's codebase.
-
"This can't be true because PHP is dead."
It lives on in the halls of financial mainframes, next to his uncle Cobal.
-
wrote on last edited by [email protected]
The worst code I've ever seen (by a longshot) was written in php.
-
That is not dead which can eternal lie.
Though HP's disturbed mind couldn't ever come up with something as upsetting as the average PHP application's codebase.
Indeed. Try making something with Symfony and you're going to have to adhere to strict theoretical guidelines that encourages you to write 200 10-line files, for a simple application. Use Drupal and well, you're going to spend ten years just to understand how it all works on that pathetic joke, use laravel and as opinionated as it is, it's probably going to make a lot more sense to you in ten months time.
Unless, you want to do something in the database other than basic CRUD. That's when ugly hacks are needed.
-
Worldwide SaaS is about as descriptive as Business Company
-
The worst code I've ever seen (by a longshot) was written in php.
I thought so too until I recently inherited some asp.net code that defies basic comprehension and has existed since well before vibe coding.
-
The worst code I've ever seen (by a longshot) was written in php.
Worst I've seen was at an old job. Another team broke up their project so nearly every Java class (file) was a separate Maven module. For folks unfamiliar with Maven, you may think that just means a different folder. That would be a Java package. Maven modules are compilation units with an entire XML file explaining the project with dependencies. So instead of their code being in one or , you know, less than five or so modules there were dozens. I wanna say a hundred but I don't want to exaggerate and don't remember.
Thankfully these were subprojects so they were still in one git repository and could all be built with a single invocation of Maven, but navigating it was a massive pain.
I try not to make assumptions about "bad code" but I can't think of any legitimate reason for that layout of one class per Maven project.
