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...
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.