News for hackers. Stuff that matters.
Re:In praise of Go or "Why I moved from Python and C++ to Go" by joe_the_user on Tuesday November 16, 2010 @11:40PM (#1912940)
I built a fairly large app with Python years ago. I was neither ecstatic with then nor did I hate it. I didn't love or hate the whitespace thing then. I managed everything so it just worked.

A couple of years ago, however, I tried to help a friend trace an error in code on an active server. It came down to rewriting the code so that it looked exactly the same as before but somehow had the right whitespace instead of the wrong whitespace.

That experience left me with the strong belief that Python's whitespace approach is totally wrong and broken. Things that break in ways that are difficult to understand I can accept. Things that break in ways that are impossible to understand as such are unacceptable.

Yes, the whitespace thing can always be fixed - except on the random server where it desperately needs fixing. Systems where symbols that are meaningful don't appear are broken - it's not that a given problem with said symbol will appear often. It's how extreme the problem is when it does appear.

Re:In praise of Go or "Why I moved from Python and C++ to Go" by grovulent on Wednesday November 17, 2010 @12:10AM (#1913002)
I've never experienced anything like this - nor do I really understand what you mean (and nor could I without actually seeing some code).

Given this, it's impossible for me to understand your claim that the white space approach is 'totally wrong or broken'. The leap from vague example (with a sample size of one) to all encompassing abstraction is too great.

Having said that, I'm keen to ensure that I don't pursue the wrong path. I picked python because many people I respected said it was a good 'jam for beginners'. But that can't be true if it's 'totally wrong and broken'.

Care to pony up with a proper account of your position?

Re:In praise of Go or "Why I moved from Python and C++ to Go" by silentbicycle on Wednesday November 17, 2010 @12:49AM (#1913079)
I think it's a corner case.* While I don't personally care for Python anymore, I still think it's a good beginner language.

* And after debugging production issues with proprietary compilers that had almost perfectly reliable hot-code loading...that's pretty minor. Not mixing up tabs and spaces probably covers it.

Re:In praise of Go or "Why I moved from Python and C++ to Go" by aaronblohowiak on Wednesday November 17, 2010 @12:40AM (#1913055)
It was probably a tabs vs spaces issue, leading to an oddity of a block of code at the wrong depth.

The fix is to simply accept only tabs OR spaces as valid whitespace... then again, this is one of the things that annoys me about make, but I digress..

Re:In praise of Go or "Why I moved from Python and C++ to Go" by joe_the_user on Wednesday November 17, 2010 @04:03PM (#1915739)
As I said, there are lots of fixes.

But all the fixes depend on completely controlling the environment and the code production process. They work but they add "global control" need that is a bit more extreme than other languages. This qualifies as a "weird fragility" in my mind. Considering how many other levels of any given system might have weird fragilities, why be willing to accept language that guarantees you'll need to deal with such fragility by it's very structure?

I'm sure I over-stated the problem when I first stated it ... but whenever I remember the situation, I feel the terribleness of it so I don't think it's unimportant.

Re:In praise of Go or "Why I moved from Python and C++ to Go" by aaronblohowiak on Wednesday November 17, 2010 @04:21PM (#1915802)
I meant to suggest that the language be made in the language. Changing your process to accomodate a misfeature is not a fix, it is a work-around. We agree that this is a case where computer-enforced order is more important than programmer freedom, though you could create human processes to work around the danger that such freedom affords you.

I'm starting to get to the point of just wanting sexps everywhere...

Re:In praise of Go or "Why I moved from Python and C++ to Go" by xiongchiamiov on Wednesday November 17, 2010 @01:12AM (#1913133)
...or just use a semi-decent editor that tells you when your code is indented inconsistently.

I think we solved this problem like, 20 years ago or something.

Re:In praise of Go or "Why I moved from Python and C++ to Go" by dalke on Wednesday November 17, 2010 @04:11AM (#1913565)
Or start Python in '-t'/'-tt' mode to generate warnings/errors on inconsistent tab usage.
Re:In praise of Go or "Why I moved from Python and C++ to Go" by silentbicycle on Wednesday November 17, 2010 @01:13AM (#1913134)
Well right, but make already had like six users, so it was too late to change. ;)
Re:In praise of Go or "Why I moved from Python and C++ to Go" by cdavid on Wednesday November 17, 2010 @12:06AM (#1912993)
I have programmed in python for almost 5 years, with medium-large (several 100kloc) projects, this has never ever been an issue. If you mix tabs/space, you can have issue, but that's nothing that any decent text editor cannot fix/highlight.