And Silicon Valley becomes slightly less satirical.
Developers who use spaces make more money than those who use tabs
181–190 of 690 posts
Re: Developers who use spaces make more money than those who use tabs
#182Almost certainly a result of the spaces cabal and the (often unspoken of) prejudice against tab users. Don't think you make hiring decisions based on tabs vs spaces? Well you're part of the problem, then. I'm building an app to help you easily email your congressperson and ask them to create legislation requiring space/tab equality. This has to stop. Please consider donating to my Patreon.
It's not really prejudice if those 'tabbies' are just inferior, is it?
I can't believe that in 2017 I'm reading comments containing blatant spacial prejudice on Hacker News of all places.
Re: Developers who use spaces make more money than those who use tabs
#183Earlier quoted context omitted.
In fact, tabs are better for compatibility: other people might like other indentation sizes. If you keep your stuff consistently with tabs, and use spaces for alignment instead of having your IDE auto-replace tabs there as well, your code will look great with whatever tab size someone chooses. And extra pro: in dumb editors, you automatically get the right thing.
Tabs are only better for compatibility if you know that no one who touches the code will ever use spaces.
We enforce that: spaces break linting.
Trivially easy to set up your editor correctly once (if you even need to) and now everyone gets their preferred intenting size
Re: Developers who use spaces make more money than those who use tabs
#184Clearly, you have to pay people more to use spaces, free market at work.
Re: Developers who use spaces make more money than those who use tabs
#185Earlier quoted context omitted.
> Tabs for indentation; spaces for alignment; If you try this, it fails for people who use a different tab size than you, which is the whole supposed point of using tabs. But yes, the correct answer is don't align. Utter waste of time.
This entire thread is why I love gofmt so much. I haven't thought about this useless bullshit for years.
Myself, working on an old open source project, I just don't care. Match the nearby style best you can, use your own style on new code, who cares, get on with your work.
Re: Developers who use spaces make more money than those who use tabs
#186What about using tabs that render as spaces in the IDE?
Re: Developers who use spaces make more money than those who use tabs
#187Money isn't everything. Tabs live forever!
Re: Developers who use spaces make more money than those who use tabs
#188The most confusing thing about this result is that go shows a high level of space-preferential salary difference. Go programmers who use spaces make ~20k more (at the median) than developers who don't.
Only, in Go, you don't have a choice -- gofmt enforces tabs only (with spaces for alignment). So something seems odd there.
Re: Developers who use spaces make more money than those who use tabs
#189Tabs vs. spaces. 2 vs. 4 spaces. It's an endless discussion. We finally compromised and we're using 3 tabs.
You sir/ma'am win the internet today.
Re: Developers who use spaces make more money than those who use tabs
#190Earlier quoted context omitted.
Almost everyone I know who uses spaces or tabs does so because that's either the default on their IDE, or for their language. So this holier-than-thou argument holds less water than the sun. On the other hand, I find 2-space-indented code unreadable; in fact, 4-space wide indentation is the only size I find to be readable. I know plenty of people for whom that isn't the case. Using tabs lets the reader set the indent…
Actually they all boil down to 'someone else, or another IDE that you haven't configured just right, will mess your tabs and make the code hard to read' :) They're fine for solo projects i guess, if you only ever use one editor. Edit: Also, in the long run the best thing you can do to your code is to make it easily readable. You will forget what you did. Not to mention your colleagues that have never seen it. So time…
> So time spent aligning parameters to make code more readable is well spent, if you ask me.
How is this[1] more readable than this[2]?
[1] https://github.com/HearthSim/python-hslog/blob/5a6ad9a29a7d4...
[2] https://gist.github.com/jleclanche/ef40058731061e26d218e2a4c...
Let the lines get long enough and the latter is actually quite a bit harder to read; try to follow the variable all the way to its value and you might actually jump and be one line off.
I deeply care about readability and code style, that's why I'm replying here :) And in all the codebases I have read and written, alignment has consistently been harmful to readability and maintenance.