3 ms·
> It’s intent is to allow a given codebase to maintain a consistent style (eg camel vs snake) even when making use of upstream libraries that use different styl
by IshKebab 5y ago
> It’s intent is to allow a given codebase to maintain a consistent style (eg camel vs snake) even when making use of upstream libraries that use different styles.
This doesn't make sense. For an entirely new language you can just have the entire ecosystem use the same style, e.g. like Rust does. Or even Python!
- stavros 5y agoI'd agree, if you want a consistent style, ship a formatter with your package manager, like Rust does with `cargo fmt`. If it's there by default, it'll quickly be a standard.
- aEverr 5y agothere are many packages and maintainers of such who just dont give a damn about the formatter or the style, some people just *want what they want*
- stavros 5y agoSure, but there's a standard formatter, they become a small minority.
- aEverr 5y agoand with style insensitivity they become a non-issue?
- stavros 5y agoThe compiler might not be sensitive to style, but *I* am.
- atom_arranger 5y agoI guess the best thing would be having a formatter that can switch the style for you locally. I don’t think Nim has this currently, would be neat if they did.
- stavros 5y agoI don't think most people care about a specific style, as long as it's consistent. That's why I love Black, we all disagree with it equally, but each for different reasons.
- hexo 5y agoIt actually makes a lot of sense. I personally don't want to touch .Net langs because of their PascalCase and camelCase coding style which I find very unfortunate arbitrary decision. And well, didn't really want to get into Nim because of camelCase but since I've learned about this feature I'm reconsidering again.
- maleldil 5y agoDo you really dislike camelCase that much to avoid an _entire_ ecosystem because of it? I prefer snake_case too, but avoiding a language because of a minor convention like that seems weird.