I'm a php developer

I don't like
If (something) {
//code here
}

I like
if (something)
{
//code here
}

Sorry.

EDIT:

However, in javascript, I'm fine with the first example. I may need professional help.

Well, you are close to psr-2 standard.

Class definitions and method braces go on a new line.

If else statements however, would require to be on the same line.

It ain't a crime to go against this. But, you know :P

Depends on de amount of conditions how I do things... I always start checking all negative things though....

if(
idontlikethis
){
return fu..
}

if(
idontlikethiseither
){
return fu..
}

return whateverwhenilikeyou;

Senseless whitespace

There are bigger fish to fry than where the brackets are. It's normally all the shite inside them that pisses my off rather than the brackets themselves.

Reconfigure your phpcs and/or phpmd (i dont remember which). You can adept PSR for your needs, like I did. I heavly dislike some portions of PSR but love others.

I like #2 more too. I was raised on the C family, its what we do and for me at least code reads much cleaner with #2. #1 is more compact and looks fine, but #2 makes things very obviously separated into chunks and my eyes and brain have a better time reading and compiling it with those "mental" separators

@Hazarth

exactly how I feel

Respect the fucking PSRs standards if you're writting php.

Why do you prefer the second option? Also is the style called Allman or is that just something I heard?

Try pl/SQL and VB, then you get

If blah Then
Some code
End;

@Lyniven What if I say no? Some PSR things are annoying me and I much prefer writing in coding standard that feels most readable?

a?b:c;

That's good enough for me.

@ewpratten <presses ++ very hard>

or maybe I should use this... ?

https://github.com/FriendsOfPHP/...

@ewpratten

yeah, ....but that becomes a bitch to untangle and add lines if you ever need to

Holy shit you're gonna love GOLANG

I'm a top one guy.
It stops me from adding ; at the end of a if and executing the next line regardless.

But each to their own.
I do like a lot of the PSR's but something.... meh.

ew

@zuley That's Allman style, yes.

I usually use that bracing style, unless there's a coding style that says otherwise. For me it's easier to see how the code is structured that way.

@DubbaThony if you don't respect the most widely used and recognized standards, I'll just assume you don't respect anything else in your code, write bad quality, unbearable shit code.

@Lyniven Assume what you want, I respect most of PSR but rest I change and stay consistant. For example:

if () {
or
if() {

One of them is PSR second not. Guess which drives me absolutely nuts?

Edit,
Oh, and Im also tab guy, not spaces guy. So thats another thing i change. That may be your shittieness measure, whatever.

@DubbaThony you share the same thoughts as i do for some of the PSR's :D

@C0D4 So you know, we are making shitty unmaintainable code, so here is that 😂😂😂

@DubbaThony one mans shit is another mans treasure... 😅

@C0D4 Does that mean we should fork PSR and fix it in some regards and call it "unmaintainable but treasure"?

@DubbaThony nah, I'm thinking "PSR - the right way"

@C0D4 oh ya. Definitely.

Or maybe simple tool that unfucks and fucks up code (changes between exacly user's favourite flavour of PSR to fully-fleded PSR just before push and reverse on pull)...

That's actually interesting idea and I guess its doable with existing tools so it would be simple bash script. hrmmm....

@DubbaThony

I'm in marketing 20 years

What you described would definitely be a hit/sell/famousgithub/ etc.

You should do it if you want those things, cuz it's guaranteed going to take off, especially if you consider that PSR can only become more nitty, not less. The timing is right on.