3 ms·
But when the language/tooling enforces it, you've made language choice a proxy for style choice. A large part of what makes me stick to Ruby over Python for ex
by vidarh 9y ago
But when the language/tooling enforces it, you've made language choice a proxy for style choice.
A large part of what makes me stick to Ruby over Python for example, is that I can't stand languages with significant indentation. It may seem minor, but it isn't to me, to the extent where I avoid Python whenever I can.
When your language enforces formatting like that, people will choose or choose away the language over the formatting.
It's that important. Especially with so many languages to choose for that you can often pick one that is sufficiently similar.
- tqkxzugoaupvwqr 9y agoGo enforces a style because all code, written across different teams and organisations, should look the same so anybody can pick up anybody else’s code and read it with ease. There are no differing styles in different libraries. It’s very harmonic. What I can’t stand in other languages is the Laisser-faire attitude regarding styles. Some people put whitespace here, some there, some put the curly brace here, some there. How about some consistency across all codedbases?
- vidarh 9y agoI'm not willing to put up with harmony at the cost of the code I have to spend most of my time reading being formatted in ways I don't find optimally readable. Making people who care about formatting to the extent I do refuse to use the language is the cost of tools that enforce those kind of rules. That's of course their choice, just as it is mine to stay clear of tools (and languages) I don't consider worth my time.
- UncleEntity 9y ago> A large part of what makes me stick to Ruby over Python for example, is that I can't stand languages with significant indentation. More like 'consistent indentation' methinks. I still have nightmares about trying to merge some GSOC student's code from their branch to trunk where the indentation was all over the place, it was so bad that lint couldn't even figure out what the hell they were up to -- well, I think lint was crapping out on macros more than anything but still... So...someone got to put on their resume they did a GSOC for Blender but the work they did was basically wasted since it wasn't possible to clean it up enough to merge.
- vidarh 9y agoNo, I very much insist on consistent indentation. Yet what I consider consistent indentation and what a given tool might consider consistent indentation does not always agree. But specifically with Python my problem is that I've yet to see any setup where things like e.g. cut and past works consistently without regularly mangling indentation in various situations. Then having the indentation convey semantics is a nightmare.