that is
they could look
like this that is
they could look
like thisDidn't we learn something from Makefiles here? Does that 'tab' look like 8 or 4 spaces to you?
When did that happen?
If you simply enable option in your editor to make white spaces visible (i . e. you can tell the difference between tab and space), the problem becomes silly.
I personally like to use tabs for indentation, because of huge flexibility being able to change tab size (which changes indentation) as needed, but that just me.
That strikes me as an even more valuable property for configuration, which is more often accessed by multiple people and tools and more often as a distraction from other work rather than the primary focus.
You or the other team of developers/maintainers/sys-admins looking over or patching this particular file. Using whatever default editor they prefer with whatever config an tabifying/untabifying behaviour that has.
Or maybe they are applying a patch produced on a different system with different tabulation? Or the other 2000 common ways for accuracy to go out the window.
> That strikes me as an even more valuable property for configuration
So you'd like to deliberately make the configuration system more brittle for absolutely no gain?
Yeah. Count me up for anything else. I personally prefer s-expressions, but I would be willing to go the full mile with pretty much any format NOT based on whitespace. Whitespace is bullshit and depending on it even more so.
I don't think you understand the philosophy behind FreeBSD: it's about creating a predictable and reliable OS. This goes against those goals. Simple as that.
I like Python but this is not actually true. you only need to be consistent within a block, or be more deeply indented than the outer.
You can have different indentations for the if and else clauses!