Open Source Contributions More Important Than Tabs Vs Spaces For Salary (opensource.com)
Jason Baker, a Red Hat data analyst, doesn't believe developers who use spaces make more money than those who use tabs. An anonymous reader quotes Baker's blog post:
After reading the study one data scientist, Evelina Gabasova, performed some additional analysis and came to a slightly different conclusion, which feels a little more precise: "Environments where people use Git and contribute to open source are more associated both with higher salaries and spaces, rather than with tabs." In other words, if you're at a company where you're using version control and committing open source code upstream, you're statistically a little more likely to be a space-user and a higher wage-earner.
Even across all experience levels, contributing to open source still correlates to higher salaries, Gabasova concludes. "My theory is that when diverse people are working on open source projects together without enforced coding style, the possible formatting mess is nudging people towards using spaces simply because the code is consistent for everyone.
"This is just one of the possible theories, I didn't look to see if possibly language communities that use predominantly spaces (like Python or Ruby) are more active in open source."
Even across all experience levels, contributing to open source still correlates to higher salaries, Gabasova concludes. "My theory is that when diverse people are working on open source projects together without enforced coding style, the possible formatting mess is nudging people towards using spaces simply because the code is consistent for everyone.
"This is just one of the possible theories, I didn't look to see if possibly language communities that use predominantly spaces (like Python or Ruby) are more active in open source."
Wait, there is no connection between spaces, tabs, and how much I make? But I just spent days going through all my code and replacing and reformatting with spaces. Please don't tell me I have to be worried about curly braces.
If you want news from today, you have to come back tomorrow.
Score one for correlation vs. causation.
https://xkcd.com/552/
Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
Spaces -> the person who writes the code decides how its indentation looks
Tabs -> the person who reads the code decides how the indentation looks
Sometimes I set tabs to be 4 spaces, sometimes 8, sometimes even 2 spaces. However, if the formatting is all done with spaces I don't get that choice. I find tabs more empowering to me personally and I believe that I use them I empower those who read my code.
We understand tabs. That is why we don't use them. If you can't figure out why tabs are a bad idea that is an indication of your incompetence, not ours.
Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
Unless you originated the project, the number one rule is consistency. If you do a lot of contributing to open source then you will find a lot of projects with spaces... and regardless of your preference you will stick to that style if you want your code to be merged.
I'm a tab guy, it's just a preference... Yet all of my open source contributions to projects other than my own use spaces.
Read this a while back, had to go digging for it:
https://opensourcehacker.com/2...
P.S. The commentary is more insightful than the article itself.
What are the chances you are submitting to open source and having a high salary?
Pretty high - most (all?) of the large tech companies have started, and/or contribute heavily to massive open source projects.
Apple - WebKit, clang, llvm, Swift, BSD, ... ... ... ...
Amazon - Outlier? I don't know of any major open source contributions of Amazon.
Alphabet - Go, WebKit, Android, map reduce,
MS - vscode, WTS, Typescript,
Facebook - redux, React, flow,
If you're working at a large tech company, there's a pretty significant chance you're doing work on open source.
Tabs descend from the manual typewriter, where they were a poor approximation to properly-formatted columnar layouts. Unfortunately now they join several other forms of white-space (because of Unicode) which are sometimes impossible to distinguish from each other. The safest thing to do is thus to only use space for horizontal spacing. Certainly software should not distinguish white-space characters differently. I'm looking at you, "Make", and yes I've heard the story about it being too late to change because there were already 12 users.
Bruce Perens.
When using Emacs, the tabs/spaces argument is moot.
When spaces are used, Emacs handles that automatically.
When tabs are used, Emacs also handles that automatically and elegantly.
When both tabs and spaces are used, Emacs also handles that automatically, elegantly, and beautifully.
The world might be a much better place if we all used Emacs.
Kriston