Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
drndavi548yif ($something == $something_else) {
return true;
} else {
return false;
}
It will piss me off a little until my last breath -
@JakeHL I suppose you're right. Unless someone has a reason verbosity is bad. Lol
-
JakeHL6658y@shittywebdev
I mean, extreme Verbosity to the point of inefficiency might be a reason, but op's post isn't too bad :) -
bgarcia38y@drndavi definitely the most common example from my experience. it makes it harder to read, particularly when you are looking at a 1000 lines of php spaghetti code with just about everything in the global namespace...
of course there's also this gem:
if(a) {}
elseif (b) {}
else {
x=true;
} -
arekxv10548y@drndavi Or worse:
return $something == $somethingElse ? true : false;
I see this in many places... :/ -
arekxv10548y@JakeHL I'm up for verbosity as far as it removes the need for comments, any other than that is too much :D
if (boolValue == true) ...
I know it works, but just kill me now.
undefined
cs class is pointless