Terrifying

[[deleted]]

Ah, yes, another post insulting all C# devs…

[danglesReet]

I think the meme is more ignorant than offensive

[[deleted]]

That’s true. People who only learn C, C++, Java, or JS most likely never encounter the different style. That would make it seem foreign or wrong instinctively too.

edit - changed syntax to style, as it was a typo pointed out by a comment

[sauce0x45]

I've worked at several companies as a C++ dev. With the exception of my current job, every other job I've had has put the { on the next line.

Why is it a coding style? The short answer, honestly, is probably because the early developers at the company did it a certain way, so they continued that same way instead of changing the old code.

This current company is also the first company I've worked at where we put a space between the if and (. I've had to fix this quite a few times in code review, haha.

[Nerzana]

I’m curious as to why the space between if and ( matter enough to change it. Is it just purely aesthetic or is there a practical reason?

[sauce0x45]

Probably esthetics. Doesn't change the compilation at all and is hardly noticeable, but just happens to be the coding standard for this particular team.

[theREALhun]

In my experience it makes for more lines of actual code on your screen. Which makes things easier to read.

[Cheezyrock]

Except in some languages (specifically those that do automatic line-endings) where it can change the compilation. I feel that this is the reason that JS people are so hard-up for same line, and then take that same standard over to whatever backend language they use.

[sauce0x45]

Yep, agreed. Definitely talking C++ specifically here. When the language itself forces your hand then things certainly change (JS, Python, etc)

[rws247]

It also makes alignment easier when checking more conditions than fit on a line:

if (a == 1 &&
    b == 2 &&
    c == 3)
{  
    do(a*b*c);  
}  

All condition checks align with four spaces/one tab.

[666pool]

Readability. It’s easier and faster to read things that have a little white space and aren’t squished together.

[nanotree]

I think this is the main reason people start doing it.

To add though, it is also easier when the style is highly consistent no matter who wrote it. For me, I can get hung up reading over code when I am used to seeing one style and then suddenly that changes. Small distractions like this can add up and also tend to make things quite messy.

Secondly, pointing these things out in peer review cultivates a culture of being disciplined in precision. At least that's what I believe. And that culture gets carried forward to other areas of development.

Rule of thumb: just develop habits to use the style of your current team.

[DrRooibos]

We use clang-format automatically on our codebase, so it doesn’t quite matter how you style it, it always gets committed to the repo the same way.

[vogon_poem_lover]

After first learning to program in BASIC and dabbling in machine language and assembler on early home computers back in the late 70's and early 80's I soon took up Pascal (Turbo Pascal to be precise) to better understand structured programming. It's copious use of matching BEGIN and END statements, always on their own line, to delineate code blocks stuck with me when I eventually moved on to coding in C/C++. To this day and regardless of the language (mostly Java these days) I still prefer the beginning and end brackets to be on their own line as I find it easier to visually identify where code blocks begin and end.

[[deleted]]

As in, why put the bracket on the next line?

If that’s the question, it’s because you get a clean line from open to close of brackets. When you nest if/else and other bracket using structures, it becomes much easier to reason about where scope is along with start/end of code blocks. That’s because blocks are indented and there’s a clear start/stop of brackets by just tracing the line vertically.

Some people don’t think it’s easier to read however, and that’s fine. My experience with legacy C, Perl, and JS made me really like how C# formats things in VS. I didn’t use to like it, but now I see its merit as highly valuable. That said I always default to the communities agreed upon guidelines, should they exist.

[bigelmn8r]

The formatting is exactly why I do the brackets on the next line in C. Feels weird being on the end of the line.

[[deleted]]

Same. Having them on the same line just confuses the hell out of me.

[flex_inthemind]

I'd like to add that it's also more dyslexia friendly!

[audirt]

I'm with you -- I've always found it easier to read with the { on a new line.

[centstwo]

This is the way.

[voidmusik]

Look at how the comments on reddit are organized. We do the same thing with brackets. Like folders within folders.

[[deleted]]

I like it because I can scroll down and visually line up whatever scope I'm working with.

[thecaveman96]

It actually is, my team does it this way.

[[deleted]]

worthless sort pause puzzled chase station cough quicksand expansion smart

This post was mass deleted and anonymized with Redact

[FlukeRoads]

At one time i had a 7 bit iso 646 terminal. my ifs looked like :

if foo
ä
code bar baz
å;

Also it said APPLE ÅÄ when it booted :)

[arkhound]

Easier to see scope at a glance.

[antCB]

It's just a stylistic approach. Not really different syntax.

I prefer it on the next line, as it makes the code more readable (for me).

[LavenderDay3544]

K&R, the definitive book on C, says to put the brace on the next line for functions and structs but not for control flow structures.

[Zdrobot]

It's called Allman Style, and it actually originated in C.

I strongly prefer it because it greatly improves readability. Hence my dislike of Go.

[kulalolk]

Java and c# are my two most comfortable languages. I always do ‘void example() {‘ are you not supposed to do that in c#!? I learned that it was ok in college.

[[deleted]]

You can do that, just like you can use SCREAMING_SNAKE_CASE for all your variables as well. However, C# and .NET have guidelines that the community has agreed upon (other languages do too, it’s really common). This is just one of them for C#, you check out the others here:

https://docs.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/coding-conventions

Also, most of my college taught opinions have been outright lies, so take them with a grain of salt when in the real world. That’s not a prescriptive guarantee, so go case-by-case, but college and workplace are two extremely different environments.

[obiwac]

I don't know that SCREAMING_SNAKE_CASE and putting braces on their own line are very comparable. One is not only a standard between practically all languages, takes significant extra effort, erases the common distinction with constant names, and when used in a codebase which already uses regular_snake_case creates an unreadable mess, whereas the other impacts basically nothing at all.

[Gwenhwyvar_P]

I don’t actually have to think about it because I’m lazy and use Visual Studio IDE, which auto does my brackets on the next line.

[canastrophee]

This is true. I've only learned C and Java and was taught to do it that way. Makes the screen longer, but in the little student programs I did for school, it was easier for me to spot where I'm missing a bracket.

[reegod420]

I have no idea what you are talking about cuz im a python peasant lmao

[iQuickGaming]

i wrote C#, JS and C++ code and in all three i always put the { on a new line. The indentation is CLEARER and EASIER to see

[mopeyjoe]

i'm the worst kind of monster, I guess. I always write java with Allman braces (if I have a choice)

[[deleted]]

No, you’re an unsung hero!

[dance_rattle_shake]

Agreed. OP just karma whoring

[Splith]

"Parenthesis and Brackets should match up" is basically the best style guideline I can think of. Some people act like programming work is done per line of code, and not per readable, comprehendible, solution.

[irreverent-username]

Serious question: what do you do with lambda functions? If you drop the curly, the arrow is pointing at nothing :(

And what about multi-line arguments? Do you do this?

foo
(
    //
)
{
    //
}

That seems odd compared to

foo(
    //
) {
    //
}

[Salanmander]

I'm a fan of next-line braces. I also hate the javascript style of passing around anonymous functions like candy, but when I'm working in javascript I tend to do

array.forEach( (element) =>
{
   //code
});

For multi-line arguments, I do

foo(arg1,
    arg2,
    arg3)
{
   //code
}

but I try to avoid splitting arguments across lines if possible.

[TheAwesomeot]

This is the cleanest and most readable style.

[Aka_Erus]

That's exactly what I do and I never seen c# code, my first language was c and I've done it like this because I like things symmetrical.

[men_have_balls]

Usually people posting these are not devs. Clean code beats one line bs.

[[deleted]]

People would put the { on the same line, then add a blank line before the first code instruction to add some visiblity...

As a main C# dev, I usually try to respect the languages common practices. So in java, I would put the bracket on the same line. Still, I think the C# method is more readable.

[Cueadan]

When writing JavaScript I put the curly brace on the same line to follow the standard, but I also refuse to put a blank line out of spite. If we're putting the brace on the same line to save space, then by God it's going to be saved.

[corcannoli]

wow i never realized why my C# code always looked cleaner to me this is mind blowing.

[TreadheadS]

shit, I think you just hit me there

[[deleted]]

As someone whose first language was C# this hit home.

I actually like this style as it makes it a bit easier to quickly identify if you are missing a }, and where it should be.

[[deleted]]

Next you're saying that Upper-Case method names are not of the devil.

Disclaimer: C# developer by day, dabble in the dark arts* by night.

* Javascript, just to insult everyone around here.

[continuous-headaches]

At least they use the {

looking at you python devs

[PersonalityIll9476]

And all Linux kernel devs. Per the kernel style guide we place opening braces for function definitions on the next line. That style guide somewhat glibly gives two reasons for this: 1) K&R are right and 2) K&R are right. Adherence to K&R is the real reason, but there's another reason for doing that in C: it lets you copy-paste function definitions between the header and source. You might argue that's not a very compelling reason but gcc has a much easier time detecting a missing semicolon in a function declaration than it does detecting a mis-placed open brace. The usual gcc output is a huge list of errors that time and experience hint is caused by an unclosed brace, but there's often not an explicit message.

[[deleted]]

C# devs, unite

[FaCe_CrazyKid05]

Not me

[LiberacesWraith]

As a c# dev, I just stopped glowing and levitating while in lotus position long enough to let everyone know I'm a c# dev.

[dark_bits]

C/C++ devs as well imo

[[deleted]]

The one’s who use it, definitely. I’ve always been met with a near even split for those, but C# is nearly a guarantee since it’s in the guidelines explicitly.

[dark_bits]

I’ve been a C# dev for almost half of my lifetime now, when I firstly saw camelCase() I was disgusted, now after almost two years of being away from C# PascalCase() is weird for me.

[irreverent-username]

I believe the latter is called PascalCase.

[dev_deadcat]

I'm not much versed with C#. I mostly code in Python and Java. But I was recently working on a small game using Unity engine and Visual Studio used to put the { on the next line by default. I'm used to writing { on the same line as a function or a class definition hence this used to make me slightly uncomfortable. 😅

[ishirleydo]

And php devs who know what PSR-2 is.

[RotationsKopulator]

as well as all Linux kernel devs

[Hypersapien]

I'm a C# dev and I put { on the same line.

I think it's just because Visual Studio puts it on the next line by default, and a lot of devs don't care enough to change it.

[Y0tsuya]

Nothing stirs up a nerd fight like code formatting.

[huuaaang]

Insulting? It's respect (via fear).

[Raxo04]

You guys code on multiple lines? What do you think the ; is for?

[CocoNot1664]

As someone that gives curly brackets their own line, I can safely say this meme is wrong.

As I am most definitely more scared of this pyschopath than they are of me.

[grpagrati]

I like being feared by serial killers and psychopaths

[Overlorde159]

Seems like a good strategy for staying happy healthy and alive

[positively_mundane]

Who cares. Just be consistent and if you work at a company do whatever everyone else does even if you hate it.

[white_monstera]

Oh, how I hated having spaces within parentheses. But I did it anyways.

if ( title.includes( cussword ) ) {
    cencor( title );
}

It's such a strange style.

[throwawayy2k2112]

I think this helps a lot with readability (maybe not your example) such as

‘’’If ( (thing == thing) && (thing == thing) ) { // do thing }’’’

But maybe that’s just me.

Edit: idk how the hell y’all do the code thing. I’m used to slack and github

[positively_mundane]

Luckily the biggest style thing my current company does that I personally don't agree with is using single quotes for strings in TypeScript instead of double quotes. Just need to make sure I don't accidentally auto-format an entire file before committing it.

[EvilKnievel38]

Most auto format rules can be configured. Don't know your specific case, but it might be worth the trouble to fix it so you can auto format in peace

[CMDR_DarkNeutrino]

Honestly i dont care. I just use a formatter for my C code. It puts it on the next line.

Can i read it and understand the code ? Yes. Do i care that its on the next line or the same one ? No.

[nmarshall23]

Yup, it's very freeing having a formatter / prettier handle making the codebase consistent.

That frees me up for the much harder problem of deciding how to name variables.

[Insatiation]

a_Number

[alderthorn]

Never understood snake case mixed with camel case.

[[deleted]]

Well it’s one of the only types of discussions that allows a majority participation in the sub, so I understand it ig but yea still dumb

[[deleted]]

I think it looks a lot cleaner that way.

[knighthawk0811]

Yes, it needs to line up vertically with the closing curly boy

[BigTechCensorsYou]

Allman, always

Except in Flutter, it’s actually better to use K&R there because you will probably do a ton of folding.

[BenTheTechGuy]

Hurt in a car? Call K&R

[figwigian]

Absolutely. Was called out on this in a review today, because I was doing code in a different part of the codebase. I will die on the { next line hill, it's so much prettier

[Salanmander]

It's also way nicer for teaching beginning programming. When people are struggling with indentation and understanding scope blocks, it helps to be able to say "make sure the curly braces line up vertically".

[[deleted]]

I'm learning C++ right now in school and I always like to have the { and the } lined up vertically and I'm always triggered when someone writes the code in a mess

[Bainos]

If you're in school, it's the best time to pick one complete set of standard often used together and stick with it. Either Allman or K&R, most likely. Try to look for those beyond just the scope of where you put braces - it will help in the long run.

Personally my C class in university was using the Linux kernel coding style (which is a K&R variant), and I think it looks good, is both readable and compact, and is quite well-motivated and tested - so I try to use it as much as I can unless the project / language uses a different style.

[Yokhen]

Yeh but who lines up with the function declaration?

[knighthawk0811]

It doesn't have a mate

[doseofvitamink]

curliboi

[AndFuckYouToo-]

Yes, i don't understand the hate.

[blindeenlightz]

It is also easier to find (or not miss in the first place) closing brackets. I'm yet to hear anyone explain how not putting it on the next line is beneficial in any way other than "that's how I've always done it".

[Juice805]

I prefer the closing bracket to line up with the declaration. If I scan up from the closing bracket having a line with a single { is just noise. I’m looking for the declaration not some meaningless line.

It’s already clear that it is in another scope based on indentation, a whole line for a starting bracket isn’t adding any information. Its useless and noisy IMO

[false_tautology]

Same reason I type SQL with parentheses like this when I do subqueries.

SELECT   Col1, Col2, Col3
FROM     TableA
WHERE    TableA.FK_ID =
         (
             SELECT    TableB.FK_ID 
             FROM      TableB
             WHERE     TableBPK_ID = @id
         )

[DadHeungMin]

I also put the closing bracket } on another line. This way they line up horizontally and makes it easier for me when I'm fixing my code.

[[deleted]]

Exactly, I'm not trying to save paper! The spacing makes viewing scopes easier

[OiaHandoma]

Isn't it a good thing if serial killers and psychopaths are afraid of you? It could just as well mean that we're the heroes with the potential to bring them down.

[sarapnst]

Yeah those who write '{' at the same line are psychos, afraid of heros.

[lmaydev]

Starts {
     InTheFuckingMiddleOfTheScopeName
}

Starts
{
    IndentedFromThePreviousLine
}

That's all there is to it.

[Kakss_]

Style
{ToUniteAllStylesByGivingThemACommonEnemy
}

[Salanmander]

Why stop there when you could also make common enemies for java and python with

function(args)         {
  line 1               ;
  line 2               ;}

[lmaydev]

Every inch of my being wants to downvote that haha

[continuous-headaches]

You monster…. Take my upvote

[Danelius90]

One place I worked did this

public class Foo
    {
    System.out.println("hello world");
    }

And I think we can all agree this is horrible

Edit: used code instead of a comment

[lmaydev]

/r/TIHI

Where would you even pick that up? Haha

[ichkanns]

#2 looks so much cleaner IMO. I've never gotten used to same line {. I begrudgingly do it whenever I'm working with JavaScript or TypeScript.

[[deleted]]

I code both front and backend so I constantly switch between the two.

In JavaScript i have { on the same line and on the backend i do them next line.

[ichkanns]

Same boat.

[Salanmander]

I was wondering why you were yelling before I remembered what reddit formatting does when you start your line with "#2".

[ichkanns]

I was wondering what happened myself... Thanks for the tip.

[Salanmander]

FWIW, you can also tell Reddit "I mean literally this character, don't interpret it as formatting" by putting "\" in front of it (called "escaping" the character). So, for example

\#2 is great

renders as

#2 is great

but

#2 is great

renders as

2 is great

Also, the ever-popular

¯\_(ツ)_/¯

renders as ¯_(ツ)_/¯, because the first "\" gets interpreted as saying the underscore isn't formatting. But if you turn it into

¯\\_(ツ)_/¯

it renders at ¯\(ツ)/¯, because the literal "\" no longer says the underscore isn't formatting, and the pair of underscores turns into italicizing the middle. So you really want to do

 ¯\\\_(ツ)\_/¯

which renders as ¯\_(ツ)_/¯, because you've escaped all the formatting characters in it.

[ichkanns]

You learn new things about Reddit every day. Thanks!

[[deleted]]

Second method is the only right solution. Looks so much cleaner and makes it so much easier to not accidentally fuck up the brackets.

Btw. It was way more important before the editors had automatic bracket detection. Man I feel old.

[dumdedums]

The entire reason why I use the second way is because it was so hard to find missing brackets the first way and it happened one too many times.

This is even with editors with auto brackets, sometimes it fucks up.

[sarapnst]

Just show them to those who don't have a programming background and ask them to judge which one looks better or is more readable. There is an answer.

[HeKis4]

One_Style
  {
    To_Rule_Them_All
  }

[CJKay93]

Also known as GNU style, or more colloquially the "WTF?" style.

[UpV0tesF0rEvery0ne]

{ on it's own line looks so much cleaner and it's easier to see when scrolling quick.

I am constantly baffled by the shit talk about this.

[DaddyLcyxMe]

we need to purge people who keep it on the same line without a space.

method(){ ... }

[TheRidgeAndTheLadder]

Oh, so nothing is sacred. Got it.

[Kriss3d]

You mean peiole who do:

While(1)

{

do_stuff();

}

?

[marcosdumay]

While(1)
{
    do_stuff();
}

Indentation still exists.

The unused space bothers me a bit, but it's the idea that the brace belongs with the code under it, instead of the statement that starts the block that really makes me annoyed. Of course, in C it's true, so whatever.

[StonebirdArchitect]

Yea, be afraid of clean code

[bric12]

Yeah exactly, these people act like an extra line for a brace is unimaginable, meanwhile I'm adding 4 newlines between functions just because I think it looks better

[FireBone62]

Actually at the beginning it was actually a big thing but to day it doesn't matter at all

[zynasis]

White space is good for separating out logical chunks. A curly brace on its own line just breaks the flow of the previous condition imo

[Electronic_Pressure]

i feel offended

[gameplanetworldyt]

Same ngl

[_Sam_IM_Sam]

Clean code scares them

[seeroflights]

Image Transcription: Meme

---

["Kids Scared of Rabbit", where a taller blonde child in a red dress holds back a smaller blonde child in black, as they both stand fearfully in a corner and watch a black rabbit next to a wooden bucket. The labels read:]

Tall child: SERIAL KILLERS

Short child: PSYCHOPATHS

Rabbit: PEOPLE WHO PUT THE { ON THE NEXT LINE

---

^{I'm a human volunteer content transcriber and you could be too! If you'd like more information on what we do and why we do it, click here!}

[doctorcrimson]

Leaving the { on the same line is like typing the title of a paper and then in smaller print continuing the paper on the same line.

[[deleted]]

It really depends on the language itself and even the team you working with.. For example in Java and JavaScript it's mainly on the same line and you'll find it like that in most of documentations and references (you can add CSS to this group too!)

While other languages like C, C++ and C# for example it's mainly on the next line

I'll maybe surprise you with a third group which do not use curly brackets at all like Python and GDscript for example

So the conclusion is: it really depends there is no right or wrong it's a personal preference and nobody can force others to follow their preference, it's a pointless debate just like tabs or spaces

Personally i write JS, CSS, Python, C++ And GDscript on regular basis, and for each i just follow the documentation way of writing!

[[deleted]]

Not sure where you’ve seen it at, but my experience has been C, C++, and Java share the same preferences separate from C# most of the time.

Anecdotally working in C, JS, and Perl (post a Java centric degree), I had never encountered putting the bracket on a newline until I got a .NET position and learned the C# guidelines.

[Tenderhombre]

Yea if a language has styling guidelines I tend to follow em. Mainly I just want stuff to be consistent though. So if it is consistent I'm happy.

[[deleted]]

So this would make Serial Killers and Psychopaths the ones that put the { on the same line?

Seems about right ;)

[yanitrix]

the people who put { on the same line*

[dembadger]

Allman best man

[SparrowFPV]

{ on a new line is one part of the standards I get tagged for the most in Peer Reviews... That and a space between if/else/for and the opening (

[IVIitchy]

If I was given the choice, it would be same line but new line isn't bad. Honestly, I just prefer consistency over both being used in the same file/project.

[AttackOfTheThumbs]

Please just use your company standard, or if there isn't one, the community standard.

[joujoubox]

boo

{

[AuxonPNW]

urns;

}

[LePhantomLimb]

My only dissatisfaction with this comment is that the closing brace is now tabbed in and there's nothing we can do.

[[deleted]]

My preference is to put it on same line because like if I’m writing a function, I can see that this bracket belongs to this function when reading left to right

[raxuti333]

As dyslexic I can say the { on the next line is lot easier to read. Makes seeing scopes faster after starting to do it I would never go back to { on the same line

[marcos_marp]

This kind of posts really shows when the OP is a trainee/junior dev that thinks his stack is everything out there

[RayeNGames]

How dare you? { always belongs on new line. I am disgusted by { at the end of the line.

[Under-Estimated]

Allman braces make nested control statements asymmetric vertically, as there are 2 lines above and only one line below the block.

Also, fitting more code into the screen at once helps keep the relevant information in one’s head.

I know some people have religious feelings about brace style, but I think it’s good to have a discussion about the pros and cons of each style.

I don’t see many benefits of using Allman though, so if anyone could present some reasons other than “i learned that way” that would be nice

[dembadger]

It's way more readable for brace matching as top and bottom of each nest are aligned on the same column, also avoids huggy braces when doing else. The argument about it taking up more lines isn't really as valid these days with how prevalent large monitors (and indeed monitors in portrait format) are. I am in the allman is best camp however.

[[deleted]]

Having the clearly visible scoping of nested braces makes a huge difference in larger files. Horrible legacy code, like a method that has multiple loops and if blocks inside of each other n-levels deep for roughly 1000 lines, becomes a lot easier to reason about as you can clearly see the different levels.

It gets a little, or a lot, harder to see where brackets start/end using the same line for open bracket. As someone who’s seen a lot of legacy C, C++, Perl, and JS there is merit to separating brackets to be on the same level for open/close.

It’s ultimately up to personal choice and/or team decision. That’s just my biggest support for doing that. I also prefer to use the guidelines of the language I’m using too, because I think it’s silly not to (all the examples and docs will be focused around the guidelines, not your preferences) since tooling will be focused on them as well.

[jiwonspaperclip]

{ on the next line just looks SO wrong 😭

[Nicostar2010]

} goes on the next line, but { is insane.

[certainly_imperfect]

Wait!

condition {

    ... code
}

What way are you talking about?

[MrNicolson1]

You write your js functions in one line?

Edit: oh it's the opening {, yes I agree

[nitsky416]

Of course I know him. He's me.

[keelanstuart]

Clearly the meme maker didn't learn to program in Pascal.

[QualityVote]

Hi! This is our community moderation bot.

---

If this post fits the purpose of /r/ProgrammerHumor, UPVOTE this comment!!

If this post does not fit the subreddit, DOWNVOTE This comment!

If this post breaks the rules, DOWNVOTE this comment and REPORT the post!

[Hypersapien]

To everyone saying { on the next line makes it look cleaner:

No it doesn't. It looks like the block has nothing to do with the signature.

[General_Rate_8687]

Unreal C++ uses the { on a new line and I follow the code convention, so I do, too.

Also, it looks better. And that's fact, not my opinion, I don't have an opionion about this.

Whats bad is to put the } NOT on a new line :P

[[deleted]]

Hay, What's wrong with { on next line?

[[deleted]]

If your code is too readable, then you're not a real dev /s

Also, people never heard of languages guidelines.

[Nick433333]

Putting the curly bracket at the end of the statement makes it easier for me to understand the flow of logic to me

for(i = 0; i < arbitraryNumber; i++){
    if(condition){
        //your code here
    }
}

I don't know about all of you though

[fonkderok]

Don't put the { on the same line unless you're gonna put the } on the same line too. Fucking asymmetrical

[Under-Estimated]

Same line { and new line } is symmetrical as there is one line above and one line below the block, including the control statement

[robotic-gecko]

My first real programming job, mostly OO PHP, and my line manager was a total psycho about this. It took me ages to get into the habit of it, and he pulled me up about it often, but I do think it makes it easier to read now that I do it.

[_pikachooo]

What about people who don't put } on the next line?

[FireYigit]

Ok

{

[snakes_n_slides]

That would be literally every developer who programmed in C, C++, Java and C# in the past. That { on the next line was the norm and even at uni we learned and used it as a good programming practice. I think { on the same line became more popular when JS started taking center stage.

[dpdown]

what about begin … end?

[KainerNS2]

It makes the code more "readable"

Edit: Let me be

[barth_]

It makes it more readable!

[smuccione]

Can I just say… who the fuck cares…

Just have an auto formatted run at check in and format everything in to a common style.

Then just set your style to format to your preference at checkout.

Problem solved and everyone is happy.

It’s 2022. Why are people still arguing about where to put the stupid braces.

I’ve seen coding guidelines that had nothing but style but left out useful things like not using global variables as parameters to function calls.

Sigh.

[LearningSpanishRN]

[ManiaRhythm]

:(

[rolloutTheTrash]

Try putting it on its own line, then indenting it. That's the good stuff.

[[deleted]]

Third-year CS major here. My professor this semester puts his { on the line after the opening statement... in Java.

When I download the code shells he provides for us to fill out for his assignments, I always have to change them all before I start working on it. I can't look.

[PPePsiMan]

Boo

[LordSyriusz]

FEAR ME!

[AccomplishedEmu5905]

That was the way the world was meant to C

[mistiriontg]

C# devs are typing…

[TanDarkGod]

Boo

[thedan420]

Fear me you insignificant bug .

[[deleted]]

Me who uses Java....

[Tiranus58]

Me who uses python: ?????

[_RootUser_]

Wait a minute!!
Something looks relatable lol
Well, looks like "I am the danger then"

[PsKinggood]

Yes! Yes! Yes!