/λ/ - programming

someone wishes they were using python? trying to hide the braces and semicolons

;}}}

>>49
i swear i've seen this thread before…

on another note, tabs >>> spaces. tabs save space (1 byte vs 2/3/4 bytes) and align properly with zero effort or configuration.

>>52
Probably, but what better way to start discussion than to demonstrate where we all agree?

>>52
This is ridiculous. Spaces are far better. Every character should be the same width. Tabs are unpredicatable, 4 spaces will always look the same, having a single character that is the width of 4 (or even worse 8) is just horrible. As for saving bytes that is just a dumb argument, there are so many things you can do to save bytes that I bet you don't do, why don't we just put all our code on one line to save on newline characters? Why not make every variable 1 character? Do you always leave out the braces if your conditional or loop body only has one line? Do you use the ternary operator where you can? The thing you are arguing for makes no sense. I'm one of the strictest people for optimizing as much as possible but you are trying to save a few bytes on storage of source code on disk, the biggest, cheapest storage there is. I can just delete 1 JPEG and I'll have the space for my spaces in code for the next year. You know that the compiled binary and actual program efficency will be unaffected right?

>>54
Spaces are only useful for forcing your preferences upon other people, instead of letting them choose how big the indentation on their monitor is. Only use them if you don't want to publish or share your code.

Not part of my argument, but also useful description of Unix C code style:
http://man.openbsd.org/style
https://www.freebsd.org/cgi/man.cgi?query=style

>>52
Yep that's the traditional lainchan format for starting off this flame war.

I don't get the point of this flame war either, why not argue about the colorscheme while we're at it? Light or dark? Light > dark. Fite me

>>55
Guess I'll just write my own style guide then.

>>55
The Linux style guide is also pretty good, makes a good argument for 8 character tabs too.

>>58
>8 character tabs
That was the moment when I stopped reading their style guide and vowed to never contribute to the Linux kernel ever.

>>59
congratulations

>>59
okay autist, caring more about style than function
Isn't that kinda shallow?

>>63
Its hard to write code if you want to vomit the entire time.

>>64
Not as hard as writing something for the Linux kernel.

>>59
What a major loss for the linux community. Note that a tab width of 8 is recommended, since it's tabs though, you can set that to whatever you want, so that entire point is moot.

>>104
That's one of the reasons I prefer tabs, you can set the width of tabs to whatever you like.

I think it's stupid to argue so much about something as irrelevant as motherfscking whitespace.
One could argue about a lot of things instead of just getting some work done, and tabs is certainly one of the most trivial of subjects.

>>55
>Spaces are only useful for forcing your preferences upon other people
Says the guy forcing his preferences upon other people. Spaces vs \t don't fucking matter. Just keep it the same through the whole program and don't be one of the weirdos who uses 2 spaces.

Tabs for indentation
Spaces for everything else

>>49
Tbh fam if I could set my editor up to do this for me and I could code like I was typing python, I'd rather use that. If you really trusted the editor you could even just set the color of brackets to the background color and do C like its python

>>487
>set the color of brackets to the background color
And get weird ass bugs that you can't track because you can't see the missing or excessive brackets

>>487
>>488
But here's a better idea. Write a script that takes indented text and inserts brackets around different levels of indentation. Should be a piece of cake.

>>521
So Lisp with significant white-space?

>>56
Aaaahhh.
No it isn't dark is better.
Oooohhhh I'm so mad.