mexicancartel comments on The lengths we have to go to

The lengths we have to go to (sh.itjust.works)

submitted 2 years ago by alphacyberranger@sh.itjust.works to c/programmer_humor@programming.dev

124 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] mexicancartel@lemmy.dbzer0.com 2 points 2 years ago (2 children)

Why not TABs? I hate 4 spaces cuz it can get real messy sometimes.

parent

hideshow 4 child comments

[–] amanaftermidnight@lemmy.world 1 point 2 years ago (1 child)

My editor turns tabs into 4 spaces. No more "mixing tabs and spaces" errors afterwards.

parent

hideshow 2 child comments

[–] mexicancartel@lemmy.dbzer0.com 3 points 2 years ago

Thats the problem. Then you commit. I clone it. I can't use tabs because you turned everything into spaces. Why not turn spaces into tabs?

parent

[–] CoderKat@lemm.ee 1 point 2 years ago (1 child)

I normally love tabs and it's what Go uses both by convention and it's semi opinionated formatter. But PEP-8 suggests spaces and ultimately, consistency is more important.

Not having to argue about tabs vs spaces lets us focus on the real problems, like vim vs emacs.

parent

hideshow 2 child comments

[–] mexicancartel@lemmy.dbzer0.com 1 point 2 years ago

I am aware but don't know why four spaces is suggested. Tabs are consistant and flexible. Using spaces might cause errors in number of spaces and makes code messy.

Also emacs for the win

parent