Nah, it works almost everywhere (ignoring things like nim or make that treat them differently); it&#x27;s not just a Go thing. Here&#x27;s a random page I found advocating the style for js and css:<p><pre><code>    http:&#x2F;&#x2F;lea.verou.me&#x2F;2012&#x2F;01&#x2F;why-tabs-are-clearly-superior&#x2F;
</code></pre>
And here&#x27;s what codinghorror had to say about the style:<p>&gt; This way, in theory at least, the level of indent can be adjusted dynamically without destroying alignment. But I&#x27;m more inclined to think of it as combining all the complexity and pitfalls of both approaches, myself.<p>Which sadly seems to be most people&#x27;s reaction -- basically, it might be better, but I&#x27;ll be damned if I&#x27;m going to have BOTH tabs and spaces in my files!<p>Oh well...<p>Spaces are obviously a workable solution, but there are two really big downsides: (1) it throws away information -- when should I insert or remove a indentation block of spaces? You can make your editor guess, but it won&#x27;t always guess right, and you won&#x27;t always be editing inside your properly configured editor. A tab simply says what it means and requires no editor trickiness. (2) The obvious inability to adjust the visual width of the indentation, though personally as long as it&#x27;s not too crazy I&#x27;m happy with anything from 2-8, so this doesn&#x27;t bother me. (I normally run with tabs at 4.)