3 ms·
> According to my opinion, a programming language should let a developer use his or her style. Please no. Never. moving to enforced styles freed me from having
by matt_wulfeck 9y ago
> According to my opinion, a programming language should let a developer use his or her style.
Please no. Never. moving to enforced styles freed me from having to think and debate about them. I think go set a precedent here that every new language should follow.
- infogulch 9y ago(good enough & coordinated) >>> ("beautiful" & custom) I think people underestimate the enormous cost of custom. Once style can be customized it opens up a whole universe of costs: compatibility, learning curve, project onboarding, tooling complexity. These are hours upon hours of human lives that just vanish into the abyss of pointlessness. Not just during the a style debate itself, but the mental energy it consumes at all times when "you know this specific situation would look nicer if we just made this one tweak to the style" is a possibility. The standardized style is one of the best things about Go and one of the things I miss the most when working in other languages. The usual thing to say at this point would be "To be fair there are some things I don't like about Go format, but the social benefit is worth it" but I've moved past even that. At this point I don't even give a shit about style. As long as it has something reasonable and it does it automatically. And before you write me off as never caring, I used to be that person that spends hours aligning things until they look just right, adjusting spaces to align mid-line, debating on brace & bracket placement. But it's all garbage now. Just make it good enough to read and get it out of my way. I don't like playing Microsoft Word layout games in my text editor anymore.