Nay, if the target be Americans, 'tis a rear end of size to make a Buick blush, made mobile by nothing less than the latest SUV.
The fact that the End did eclipse the sun may have deceived you as to its awesome visibility, sir.
Aw, you big fibber!
We know you want to intimidate the bullys who are thugging your lunch money,
not to mention impress the girls with your suddenly-non-pencil-neck.
[1]http://en.wikipedia.org/wiki/Jim_Webb "In 1987, he served as Secretary of the Navy...Webb resigned in 1988 after refusing to agree to reduce the size of the Navy."
Requiring a footnote for a joke is a clear indicator that it's not funny, but, then again, neither was the 2006 Senate campaign in Virginia.
I may have to stop reading any story dealing with patents because the whole thing has just gone completely beyond insane.
What part of "somebody is making a lot of money off this, albeit neither of us" did you specifically think was "beyond insane"?
I suppose the dissonance between what the patent system was intended to do, and what it has become is rather breathtaking, but "beyond insane"?
I never said you can brush off performance. My contention is that, in the overall priority of concerns, performance sorts lower than many claim.
Your point that it is trollish/flamebait to claim that requirements are ever completely defined is well taken, but actually argues in favor of a scripting language like Ruby. The fatter runtime supports a more flexible approach to following those flexible requirements, especially when the customer can't differentiate between his bottom and a hat rack. (Oh god, that was a hellish project).
It's not so much a troll as an observation that the usual complaints about performance and scripting languages are, themselves, the troll.
I work with a large number of folks who don't seem to think that anything useful can be done unless it's done in Java, irrespective of the number of worked counter-examples presented.
I think a better question is why were the braces not mismatched: because people who code much tend to indent meticulously.
The 'lightbulb' moment for Guido was when he said "well, if everyone indents, why not codify it?"
No one is out to force anyone to use anything (with the possible exception of MicroSoft).
But you still need NOAA with the data ark to handle the things that you blew off, because they seemed unimportant, but then realized that you did in fact need.
The obvious way to capitalize on the 4TB of data is to sell a new version every year with slightly lengthened scenes, out-takes, alternate endings, tie-ins, and boxed sets containing the previous and subsequent installments.
By 2015, you'll have "Deluxe Duke Spiderman 3 Power Gold Director's Cut Nukem Forever".
And you will like it.
It's also easy to draw conclusions of how cool Microsoft was early on, and how evil they are now.
Do you mean, "Using the C-language escape character as a path separator cool" or "Merging disk partitions and formats in a way that keeps people stupid (c:) cool" ?
But your point is well taken.
Can't let the bugbear-as-messenger become a distractor, for all the idea of "shooting the messenger" never seemed more appropriate.
If performance is an issue, don't you move the code to something in a compiled langauge once a) the requirements are settled and b) you're sure you actually need to do so?
I think that the rather vast body of python code freely available moves the design choice out of "WTF" territory.
Love it or hate it, it's simply not a show-stopper.
Haskell, too, has significant whitespace, though, unlike Python, you can relax the whitespace significance in Haskell.
The emacs rectangular editing features make 'sculpting' text a no-brainer:
(here is the C-h a rectangle output, noting that registers are a really powerful emacs feature):
calc-grab-rectangle M-x... RET Command: Parse a rectangle as a matrix of numbers and push it on the Calculator stack. clear-rectangle C-x r c Command: Blank out the region-rectangle. close-rectangle M-x... RET Command: Delete all whitespace following a specified column in each line. copy-rectangle-to-register C-x r r Command: Copy rectangular region into register REGISTER. delete-rectangle C-x r d Command: Delete (don't save) text in the region-rectangle. delete-whitespace-rectangle M-x... RET Command: Delete all whitespace following a specified column in each line. delimit-columns-rectangle M-x... RET Command: Prettify all columns in a text rectangle. kill-rectangle C-x r k Command: Delete the region-rectangle and save it as the last killed one. open-rectangle C-x r o Command: Blank out the region-rectangle, shifting text right. replace-rectangle M-x... RET Command: Replace rectangle contents with STRING on each line. string-insert-rectangle M-x... RET Command: Insert STRING on each line of region-rectangle, shifting text right. string-rectangle C-x r t Command: Replace rectangle contents with STRING on each line. yank-rectangle C-x r y Command: Yank the last killed rectangle with upper left corner at point.
The most compelling argument against significant whitespace in Python is that it makes generating code rather tricky, but then, how often do you do that, and is it really so hard to add another "indent" call in there to tidy matters?
Well, they could have added a nearly-canonical "...this is primarily a bug-fix release."
It goes without saying that an open source project is always fixing bugs, hopefully at a slightly higher rate than they are introduced.
The sin is not so much the integer overflow itself, as the lack of documentation as to why you let it overflow, and the justification for the misplaced creativity.
And the judge is not so much God as you yourself a few months hence, after the strange crash, when you're forced to traverse the little hell-pit you've left for yourself.
Slashdot Mirror
Nay, if the target be Americans, 'tis a rear end of size to make a Buick blush, made mobile by nothing less than the latest SUV.
The fact that the End did eclipse the sun may have deceived you as to its awesome visibility, sir.
Or, more directly: http://www.jir.com/
Check out the "Pullet Surprise"
It's just applied Ratherism: wildly inaccurate 'facts' are irrelevant in the face of 'correct narrative'.
Aw, you big fibber!
We know you want to intimidate the bullys who are thugging your lunch money,
not to mention impress the girls with your suddenly-non-pencil-neck.
No, I think that rumors also require a certain negative content to grow legs.
It'll resign[1] once they decomission the Hubble.
[1]http://en.wikipedia.org/wiki/Jim_Webb "In 1987, he served as Secretary of the Navy...Webb resigned in 1988 after refusing to agree to reduce the size of the Navy."
Requiring a footnote for a joke is a clear indicator that it's not funny, but, then again, neither was the 2006 Senate campaign in Virginia.
About overshooting and getting Plutoed?
I suppose the dissonance between what the patent system was intended to do, and what it has become is rather breathtaking, but "beyond insane"?
I never said you can brush off performance. My contention is that, in the overall priority of concerns, performance sorts lower than many claim.
Your point that it is trollish/flamebait to claim that requirements are ever completely defined is well taken, but actually argues in favor of a scripting language like Ruby. The fatter runtime supports a more flexible approach to following those flexible requirements, especially when the customer can't differentiate between his bottom and a hat rack. (Oh god, that was a hellish project).
Nah. When you've been on the receiving end of injustice, the better-late-than-never rule applies.
It's not so much a troll as an observation that the usual complaints about performance and scripting languages are, themselves, the troll.
I work with a large number of folks who don't seem to think that anything useful can be done unless it's done in Java, irrespective of the number of worked counter-examples presented.
I think a better question is why were the braces not mismatched: because people who code much tend to indent meticulously.
The 'lightbulb' moment for Guido was when he said "well, if everyone indents, why not codify it?"
No one is out to force anyone to use anything (with the possible exception of MicroSoft).
But you still need NOAA with the data ark to handle the things that you blew off, because they seemed unimportant, but then realized that you did in fact need.
But the answer was revealed recently over on
Why the Coming Data Flood Won't Drown the Internet:
http://slashdot.org/comments.pl?sid=392492&cid=21737872
Not just for Soviet submarine crewmen anymore!
The obvious way to capitalize on the 4TB of data is to sell a new version every year with slightly lengthened scenes, out-takes, alternate endings, tie-ins, and boxed sets containing the previous and subsequent installments.
By 2015, you'll have "Deluxe Duke Spiderman 3 Power Gold Director's Cut Nukem Forever".
And you will like it.
or
"Merging disk partitions and formats in a way that keeps people stupid (c:) cool" ?
But your point is well taken.
Can't let the bugbear-as-messenger become a distractor, for all the idea of "shooting the messenger" never seemed more appropriate.
Yeah. Check those "Senator Stevens" pipe charts and substitute "file formats" for "ads".
Sweet, sweet irony.
No, but they may have some underling do it.
If performance is an issue, don't you move the code to something in a compiled langauge once a) the requirements are settled and b) you're sure you actually need to do so?
I think that the rather vast body of python code freely available moves the design choice out of "WTF" territory.
Love it or hate it, it's simply not a show-stopper.
Haskell, too, has significant whitespace, though, unlike Python, you can relax the whitespace significance in Haskell.
The most compelling argument against significant whitespace in Python is that it makes generating code rather tricky, but then, how often do you do that, and is it really so hard to add another "indent" call in there to tidy matters?
Well, they could have added a nearly-canonical "...this is primarily a bug-fix release."
It goes without saying that an open source project is always fixing bugs, hopefully at a slightly higher rate than they are introduced.
The sin is not so much the integer overflow itself, as the lack of documentation as to why you let it overflow, and the justification for the misplaced creativity.
And the judge is not so much God as you yourself a few months hence, after the strange crash, when you're forced to traverse the little hell-pit you've left for yourself.