3 ms·
Because typically code will be read far more than it is written and by far more people than contributed to it. In many cases I won't have the relevant tooling i
by d110af5ccf 5y ago
Because typically code will be read far more than it is written and by far more people than contributed to it. In many cases I won't have the relevant tooling installed let alone know how to use it because I don't use that language myself. (For example, a library written in Rust that exposes C bindings whose prebuilt artifact I might download and link against.)
That being said, I 100% wholeheartedly approve of enforcing code formatting (among other things) on commit. Pre-commit hooks and linters are both awesome.
- gpderetta 5y agoIf you do not have the relevant tooling you can still read the canonical formatting. If you want custom formatting, I don't think that expecting your editor to reformat on the fly is a big ask. At the end of the day that exactly what tab proponents expect.
- d110af5ccf 5y ago> If you do not have the relevant tooling you can still read the canonical formatting. Which is often unnecessarily difficult for whatever reason, hence my initial comment. Given that tabs already exist there's literally no reason not to use them other than to intentionally spite any future readers who don't agree with your preference for indentation width. > that exactly what tab proponents expect Because that capability is built into even the most primitive of text editors since forever. Per-language formatting, on the other hand, is most certainly not.
- gpderetta 5y agoUsing just tabs you end up with misaligned code. So you need a mix of tabs and spaces (i.e. smart tabs). But nobody sane [1] would do that by hand and would rely on their editor to do the indenting automatically. At this point just ask the editor to indent on demand. [1] I'm hyperbolic, sorry if you actually do that although I pity you.