Submitted via IRC for TheMightyBuzzard
The annual Stack Overflow developer surveys often include lots of bad news. "People still use PHP," for example, is a recurring and distressing theme. "Perl exists" is another.
But never before has the survey revealed something as devastatingly terrible as the 2017 survey. Using PHP and Perl are matters of taste. Extremely masochistic taste, certainly, but nobody is wrong for using those languages; it's just the programming equivalent of enjoying Adam Sandler movies. But the 2017 survey goes beyond taste; it goes into deep philosophical questions of right and wrong, and it turns out that being wrong pays more than being right.
Developers who use tabs to indent their code, developers who fight for truth and justice and all that is good in the world, those developers have a median salary of $43,750.
But developers who use spaces to indent their code, developers who side with evil and probably spend all day kicking kittens and punching puppies? Their median salary is $59,140.
Source: ArsTechnica
(Score: 2) by Snotnose on Sunday June 18 2017, @05:22AM (7 children)
Doesn't work that way. You end up guessing the other person's tab settings, never really knowing if you've got it right.
Nowdays at the top of every file I work on you'll see something like "# vim: set ts=4 sw=4 noet:". If you use vim, which 90% of my co-workers do, things are set right. If you use something else you can ask me Whiskey Tango Foxtrot and I'll tell you it means tabstops are 4 and tabs are expanded to spaces.
My ducks are not in a row. I don't know where some of them are, and I'm pretty sure one of them is a turkey.
(Score: 2) by Whoever on Sunday June 18 2017, @05:39AM (2 children)
It does if you use tabs for indentation and spaces for alignment.
(Score: 2) by Snotnose on Sunday June 18 2017, @06:07AM (1 child)
So, you mix tabs and spaces, which is the worst of all worlds.
For fuck's sake people, be consistent. Use tabs at whatever tabstop you like. Use spaces. But don't mix them the fuck up cuz those of us who have to work on your code have no fucking clue how you set things. For C/C++/Perl/ whatever, we can deal. For Python, we're fucked. In the ass. Without lube.
My ducks are not in a row. I don't know where some of them are, and I'm pretty sure one of them is a turkey.
(Score: 0) by Anonymous Coward on Sunday June 18 2017, @12:27PM
I think you need to clarify what you mean by "mix", because so long as every line only uses tabs for indentation, there is no mixing going on.
Only if you're so inflexible as to try and force your preferred C style onto your Python code, and not attempt something more appropriate for the language.
(Score: 3, Informative) by Arik on Sunday June 18 2017, @08:31AM (3 children)
If laughter is the best medicine, who are the best doctors?
(Score: 2) by FatPhil on Monday June 19 2017, @05:40AM (2 children)
--->--->thingy->ops.krudge_wotsit(&thingy->wotsit,
--->--->--->--->--->--->--->--->··thingy->settings.wotsit_mode,
--->--->--->--->--->--->--->--->··krudge_mode,
--->--->--->--->--->--->--->--->··ostream);
have had enough experience in the real world to command anything but the lowest level of intern's salary?
Great minds discuss ideas; average minds discuss events; small minds discuss people; the smallest discuss themselves
(Score: 2) by Arik on Monday June 19 2017, @11:29AM (1 child)
If laughter is the best medicine, who are the best doctors?
(Score: 2) by FatPhil on Monday June 19 2017, @02:42PM
And it proves that you are unfamiliar with exceedingly common coding styles used by projects which have contributors numbering in the tens of thousands. Not being familiar with the field diminishes your ability to be taken seriously when discussing the field.
If you think the code needs to be "fixed", then you will never get a patch in to the linux kernel, you won't even pass checkpatch.pl.
Great minds discuss ideas; average minds discuss events; small minds discuss people; the smallest discuss themselves