For this vocal minority, resentment lingers at the very fact that the Internet is used for commercial purpose, which ignores the fact that it's a critical part of our economy.
Yeah, why WOULD it matter that the "vocal minority" got upset about you hijacking the entire internet? We're just the ones who BUILT it, you ass.
Perhaps he was writing his new book on his new Apple hardware and thinking to himself "Title...title...hmmmm...what to all this wonderful new story of mine...ah-HA!"
We also use STLport on all platforms. Its debugging implementations answer one of the complaints I've seen on this topic -- difficulty debugging.
For the other one (cryptic error messages), I cannot recommend STLFilt enough. This is a Perl script that intercepts the output from cl.exe (in visual studio . . . not sure why no one has adapted this to gcc yet) that reduces the complexity of STL error messages to a manageable level.
> Was saving the one keystroke (the close brace) per conditional block really that valuable compared to > having to mess around with all the "special" Python-friendly editors? How about the number of > times someone has has accidently mis-indented a statement?
You mean special editors like vi or emacs?:-)
Seriously, I have programmed in Python nearly full-time for the past two years. I will not lie -- I *have* occasionally had problems with indentation/formatting of blocks ("occasionally" = perhaps 10 times in 2 years). But the fact of the matter is, the productivity gains I've experienced with Python have outweighed this trivial inconvenience by orders of magnitude. Like most programmers who actually give Python a try, the whitespace thing bothered me for about 20 minutes, and then it was "oh, I just indent my code the way I normally do. How kind of them to create a parser smart enough to figure out where I want to put blocks based on my own code formatting habits, and not force me to use some annoying bounding punctuation!"
Tilting windows: I should think this would be obvious: games could interact directly with the OS. You could jiggle the entire window when shit blows up. (And just think of the screen savers . . . )
Transparent windows: From a usability standpoint, a transparent, non-modal window that appears on top of the window stack but does not get focus would be a MUCH nicer way to do non-fatal error messages than either a status bar message (too easy to miss) or a nasty modal dialog box. "Humane Interface" talks about this, as does (I seem to recall) Cooper's "About Face"
. . . Apple has done everyhting in it's power to be the ONLY company allowed to produce PowerPC based machines. Or perhaps you've forgotten what happened to Power Computing et al?
Slashdot Mirror
How many 10-year old games do you still play regularly?
If the answer is "few" or "none" then your argument is rather moot, isn't it?
Yeah, why WOULD it matter that the "vocal minority" got upset about you hijacking the entire internet? We're just the ones who BUILT it, you ass.
He wrote it longhand with a fountain pen.
> Sit on the copy until the copyright expires.
Yeah, 96 years after the death of the person who wrote it!
"There are people, especially older people who lived through the McCarthy era, who might be intimidated by this"
Well, duh!
Isn't that an oxymoron?
Dude he's the president now. Catch up.
We also use STLport on all platforms. Its debugging implementations answer one of the complaints I've seen on this topic -- difficulty debugging.
For the other one (cryptic error messages), I cannot recommend STLFilt enough. This is a Perl script that intercepts the output from cl.exe (in visual studio . . . not sure why no one has adapted this to gcc yet) that reduces the complexity of STL error messages to a manageable level.
> Was saving the one keystroke (the close brace) per conditional block really that valuable compared to
:-)
> having to mess around with all the "special" Python-friendly editors? How about the number of
> times someone has has accidently mis-indented a statement?
You mean special editors like vi or emacs?
Seriously, I have programmed in Python nearly full-time for the past two years. I will not lie -- I *have* occasionally had problems with indentation/formatting of blocks ("occasionally" = perhaps 10 times in 2 years). But the fact of the matter is, the productivity gains I've experienced with Python have outweighed this trivial inconvenience by orders of magnitude. Like most programmers who actually give Python a try, the whitespace thing bothered me for about 20 minutes, and then it was "oh, I just indent my code the way I normally do. How kind of them to create a parser smart enough to figure out where I want to put blocks based on my own code formatting habits, and not force me to use some annoying bounding punctuation!"
Tilting windows: I should think this would be obvious: games could interact directly with the OS. You could jiggle the entire window when shit blows up. (And just think of the screen savers . . . )
Transparent windows: From a usability standpoint, a transparent, non-modal window that appears on top of the window stack but does not get focus would be a MUCH nicer way to do non-fatal error messages than either a status bar message (too easy to miss) or a nasty modal dialog box. "Humane Interface" talks about this, as does (I seem to recall) Cooper's "About Face"
LB
. . . would be if they used the feedback to train a neural network, to teach it what looked "good" and "bad"
LB