1321
The lengths we have to go to
(sh.itjust.works)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 Sep 2023
1321 points (97.4% liked)
Programmer Humor
19551 readers
972 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
Tabs. But really with modern IDE it's irrelevant. Whatever the tech lead says I guess.
With things like black, flake 8 and Isort I can code however I want, list/format however I want, and commit team compliant content. The dream is real
Wait wait wait, what is this black magic and how have I not heard of it?
So you can have a local, and a team config. So at time of commit the code rules your team has selected are enforced. So if I looked at my code, on GitHub, it would look as expected by the team.
If I load it locally, it formats as I like.
Check out the cicd stuff on PRs for github
I love such formatters and wish they were even more widespread. In many cases, I really want consistency above all and it's so dang hard to achieve that without an opinionated formatter. If the formatters isn't opinionated enough, it just leads to countless human enforced rules that waste time (and lead to an understandable chorus of "why can't the formatter just do that for meeeee").
Yeah but outside of that where the code is implemented or in a documentation, tabs are still easier to look through. And it does look pretty as long as there aren't too many nested functions.
Even with nested functions tabs are neat.
Does you app have too many nested functions?
Do your app have too less nested functions?
Is your app having average number of nested fns?
And all theese can happen without modifying a single byte in the source file, unlike spaces!