News for hackers. Stuff that matters.
Re:Gofmt No Longer Allows Spaces. Tabs Only by josegonzalez on Thursday June 19, 2014 @01:32AM (#7914609)
Unsure if trolling or not. It's quite easy to have your editor represent a tab character as "n spaces" - where n is the number of spaces you find pleasing. In fact, I can't recall a serious editor where this isn't the case.

What issues have you seen with regards to using tabs?

Re:Gofmt No Longer Allows Spaces. Tabs Only by MBlume on Thursday June 19, 2014 @01:44AM (#7914637)
Grabbing some Clojure code because it's nearest to hand.

Look here: https://github.com/clojure/clojure/blob/master/src/clj/cloju...

I want the bindings being declared within that let to line up with one another. the first one immediately follows "(let [" so I need the rest to be indented six characters past where the let was originally indented. Six, not N times whatever the tab width happens to be in whichever editor someone's looking at the code in. This is the problem with tabs.

Re:Gofmt No Longer Allows Spaces. Tabs Only by buro9 on Thursday June 19, 2014 @05:06AM (#7915281)
> I want

Which is actually the problem gofmt solves.

The desire to express your individual preference through the way code is formatted is an issue not a feature.

The code may be read, maintained and handled by many other individuals during the life of the code, and gofmt is an attempt to provide an incredibly high degree of consistency in the way that the code is formatted to improve those things.

The Go way is simplicity, readability, maintainability.

Once you accept that consistency in formatting is important and a good thing to strive for, the only question is spaces vs tabs. But spaces is a highly opinionated option as the number of spaces used for indentation has to be uniform, whereas tabs allows for each individual to configure their editing tool to permit a degree of individual preference that does not sacrifice any of the consistency.

Tabs have the advantage, please configure your editor to suit your preference and not the code.

Re:Gofmt No Longer Allows Spaces. Tabs Only by gmjosack on Thursday June 19, 2014 @01:47AM (#7914644)
The way people solve that is tabs for indentation and spaces for alignment. In my opinion this is a terrible compromise as mixing tabs and spaces is sacrilegious.
Re:Gofmt No Longer Allows Spaces. Tabs Only by msutherl on Thursday June 19, 2014 @01:56AM (#7914665)
There is nothing wrong with mixing tabs and spaces. It works great.
Re:Gofmt No Longer Allows Spaces. Tabs Only by _pctq on Thursday June 19, 2014 @03:36AM (#7914864)
Provided everyone use the same tab width :)
Re:Gofmt No Longer Allows Spaces. Tabs Only by dTal on Thursday June 19, 2014 @04:25AM (#7915129)
Nope, works regardless of tabwidth; that's the point. Tabs for indent (these change size with tabwidth), spaces for alignment (these don't change so things stay aligned).
Re:Gofmt No Longer Allows Spaces. Tabs Only by oelmekki on Thursday June 19, 2014 @06:47AM (#7915494)
Oh, you're right. I should have tried it before commenting :)
Re:Gofmt No Longer Allows Spaces. Tabs Only by jsmthrowaway on Thursday June 19, 2014 @02:00AM (#7914678)
Until Python. Then it doesn't.
Re:Gofmt No Longer Allows Spaces. Tabs Only by markrages on Thursday June 19, 2014 @02:50AM (#7914773)
tabs for indent, spaces for alignment works great with Python.
Re:Gofmt No Longer Allows Spaces. Tabs Only by peteretep on Thursday June 19, 2014 @03:12AM (#7914817)
What's a compromise about it? Alignment and indentation are different semantic things, so it makes perfect sense to mix them.
Re:Gofmt No Longer Allows Spaces. Tabs Only by Glyptodon on Thursday June 19, 2014 @01:37AM (#7914622)
I'm not sure if there's an "issue" with tabs, but I have to agree that I pretty much never come across tabs in any of the languages I use regularly and find it jarring when I do so despite the obvious theoretical benefit of flexible tab widths enabling user preference.

I can't come up with a particularly good reason for it, but I'm so used to spaces at this point that tabs feel very wrong.

If anyone else has a good explanation I'd love to hear it.

Re:Gofmt No Longer Allows Spaces. Tabs Only by subsection1h on Thursday June 19, 2014 @10:17AM (#7916167)
> What issues have you seen with regards to using tabs?

How does a team adopt a standard regarding line length if their code base uses tabs and the team members specify different tab widths in their editors?

In my experience, devs that prefer tabs over spaces have a tendency to be unconcerned about line lengths, and their lines of code can become annoyingly long.

For example, the most popular Go project at GitHub[1] is Docker. Docker's code base contains Go files with lines of code that are hundreds of columns wide.[2] Gross. ;-)

[1] https://github.com/search?l=Go&q=stars%3A%3E0&type=Repositor...

[2] https://github.com/dotcloud/docker/blob/master/api/client/co...

Re:Gofmt No Longer Allows Spaces. Tabs Only by angersock on Thursday June 19, 2014 @01:36AM (#7914619)
Often different editors on a project (hell, even between computers for the same user) may display the same file different ways, and you almost always end up with weird mixes of spaces/tabs when indenting things (especially if you're super picky like I can be and really, really care about things lining up).

Simply having the editor expand tabs (to whatever people agreed on, usually 4 for C/C++ that I've seen) and save spaces, always, makes life simpler.

EDIT:

See Grandpa Zawinski's post on same: http://www.jwz.org/doc/tabs-vs-spaces.html

Re:Gofmt No Longer Allows Spaces. Tabs Only by dTal on Thursday June 19, 2014 @04:21AM (#7915102)
I hate that Zawinsky post. At the top, he says "I'm trying to avoid espousing my personal religion here, I just thought it would be good to try and explain the various sects." At the bottom, after thoroughly missing the point about semantic indentation, he says "So go forth and untabify!"