That guy whose health depends on clarification from the Attending is just going to have to wait. That or the attending should just have to sacrifice their entire lives for their jobs-- it's not like you'll ever need their help, so why give them any sort of respect or dignity?
Yes, because after all they're at liberty to take a vacation on the other side of the world, go caving, go on a wilderness hike whilst on call. Oh, wait, no they can't. If they're on call their movements are limited already.
Yes, and they can afford to pay, whereas most of the FOSS community would have to walk away because they just wouldn't be able to afford the risk. "Refund" is ok, "liable" is a problem.
The strains of postmodern philosophy which pretend that there really is no objective reality are what I was thinking. I'm willing to believe that those strains are largely embraced by neophytes, but there are lots of those to be encountered.
Actually, the notion that there is no objective reality isn't postmodern, it's as classical as it gets. It goes back at least to Gorgias of Leontini (c. 483–375 BCE). Some postmodernists have extended it by showing that there are fundamental problems with defining what we even mean by "objective reality". I think the assumptions that there is an objective reality (if we can define it) and that there are invariant rules are good assumptions, but it's important to remember that they are assumptions.
Sam36 didn't call it evolution. He said it wasn't evolution, and the reason he gave for it not being evolution is that speciation didn't occur -- not because it's natural selection, not evolution. That's plainly wrong, and shows a pretty fundamental misunderstanding of evolution. Try reading the thread again.
Clearly I'm not, because I thought evolution was a process, not an event. Silly me.
Death from stupidity is NOT evolution. It may be an example of natural selection, which drives evolution, but the death in and of itself is not evolution at all.
None of which has any bearing on what Sam36 wrote because speciation isn't all there is to evolution either.
I just can't see an advantage of micro USB over mini USB.
Because most phones on sale in Europe at the moment seem to use mini-USB, so they hope to get at least one more cable sale out of this? (Except to techies like us who already have micro-USB cables lying around, of course).
Meaningful whitespace is bad because it introduces errors
How does meaningful whitespace introduce errors? Typing the wrong thing introduces errors, not the whitespace.
(which are now invisible)
Python will tell you where they are. Actually, so will all of the editors I use.
We did learn this in the 70's.
I was using Hollerith cards into the 1980s, and whitespace is anything but invisible on Hollerith cards. I think you might be idealising the 70s a bit.
Ah, but they do! The honest ones just admit it. If you dig through various discussions on the subject, you'll find that even the most ardent Python advocates admit the problems that meaningful whitespace causes
But it really doesn't. Non-significant whitespace has all the same problems in different forms.
It's silly, if you chance to encounter improperly intended code (a rare occurrence indeed)
Significantly less rare than improperly indented Python!
It'll also apply whatever formatting conventions you, not Guido, think are easiest to read.
The thing is, once you get rid of block start and end notation, all arguments about matching braces v. one-true-brace go away. Python is very flexible in its indenting, and the only requirement is that blocks be indented. You can indent Python the way you think is best, not the way Guido wants.
Oh, I'm still waiting for your alleged "evidence".
The fact that people don't have the problems that you insist we learned were inevitable in the 70s. You put forward a falsifiable hypothesis, and a counterexample falsifies it.
No, they have a host of new and different problems caused by the use of meaningful whitespace.
Well, that contradicts your original claim then, doesn't it? And the funny thing is, Python users don't actually have the problems you think they should have.
This technique discriminates against everyone who has a creative spark (call it talent, madness or just plain good old "short bus") and in favour of Joe Mediocre Average who always pulls the same predictable score and will never ever exceed his limitations and achieve anything beyond what is expected from him.
Congratulations, you've just learned about type 1 and type 2 errors. And if you can think of any effective way of testing for cheating that completely eliminates either of them, the world of testing would love to hear from you.
People doing statistical analysis who don't understand that a standard distribution GUARANTEES a percentage of anomalous results, frankly don't have any business having a job in their field.
People doing statistical analysis who think that a standard distribution guarantees a percentage of anomalous results don't have any business having a job in that field. An absence of anomalous results is itself anomalous, but statistically it can happen.
The fact that Python users don't have the problems with whitespace that FORTRAN users did. What was established in the 70s is that FORTRAN used whitespace badly, not that whitespace shouldn't be used.
If ground control says you are landing on runway 245, you already know the heading you have to approach the airport...
That would be runway 25, and you would know within 5 degrees the heading you have to approach the airport.
Runways are numbered according to their magnetic heading, plus or minus five degrees
Plus an alphabetic suffix such as "L" or "R" in the case of parallel runways.
And your smartphone software is compliant with DO178? And your smartphone is JAA certified? What model is that?
You are so right.
That guy whose health depends on clarification from the Attending is just going to have to wait. That or the attending should just have to sacrifice their entire lives for their jobs-- it's not like you'll ever need their help, so why give them any sort of respect or dignity?
Yes, because after all they're at liberty to take a vacation on the other side of the world, go caving, go on a wilderness hike whilst on call. Oh, wait, no they can't. If they're on call their movements are limited already.
Of course it's not a two-tier internet. It's lots more than two!
Yes, and they can afford to pay, whereas most of the FOSS community would have to walk away because they just wouldn't be able to afford the risk. "Refund" is ok, "liable" is a problem.
The strains of postmodern philosophy which pretend that there really is no objective reality are what I was thinking. I'm willing to believe that those strains are largely embraced by neophytes, but there are lots of those to be encountered.
Actually, the notion that there is no objective reality isn't postmodern, it's as classical as it gets. It goes back at least to Gorgias of Leontini (c. 483–375 BCE). Some postmodernists have extended it by showing that there are fundamental problems with defining what we even mean by "objective reality". I think the assumptions that there is an objective reality (if we can define it) and that there are invariant rules are good assumptions, but it's important to remember that they are assumptions.
Sam36 didn't call it evolution. He said it wasn't evolution, and the reason he gave for it not being evolution is that speciation didn't occur -- not because it's natural selection, not evolution. That's plainly wrong, and shows a pretty fundamental misunderstanding of evolution. Try reading the thread again.
You're not a biologist, obviously.
Evolution is actually a very specific event.
Clearly I'm not, because I thought evolution was a process, not an event. Silly me.
Death from stupidity is NOT evolution. It may be an example of natural selection, which drives evolution, but the death in and of itself is not evolution at all.
None of which has any bearing on what Sam36 wrote because speciation isn't all there is to evolution either.
I just can't see an advantage of micro USB over mini USB.
Because most phones on sale in Europe at the moment seem to use mini-USB, so they hope to get at least one more cable sale out of this? (Except to techies like us who already have micro-USB cables lying around, of course).
It's a game published by Interplay Entertainment. Your move.
That doesn't rescue what Sam36 wrote. The fact that the process doesn't produce a new species in a single generation doesn't mean it's not evolution.
None of that has anything to do with what Sam36 wrote. Perhaps you should read what you're commenting to.
Can we pass a law that will make it MANDATORY to either execute or sterilize anyone who reacts to this by suggesting that we ban something?
You've just been caught under your own law. Well done.
You don't know what evolution is, do you?
Meaningful whitespace is bad because it introduces errors
How does meaningful whitespace introduce errors? Typing the wrong thing introduces errors, not the whitespace.
(which are now invisible)
Python will tell you where they are. Actually, so will all of the editors I use.
We did learn this in the 70's.
I was using Hollerith cards into the 1980s, and whitespace is anything but invisible on Hollerith cards. I think you might be idealising the 70s a bit.
Ah, but they do! The honest ones just admit it. If you dig through various discussions on the subject, you'll find that even the most ardent Python advocates admit the problems that meaningful whitespace causes
But it really doesn't. Non-significant whitespace has all the same problems in different forms.
It's silly, if you chance to encounter improperly intended code (a rare occurrence indeed)
Significantly less rare than improperly indented Python!
It'll also apply whatever formatting conventions you, not Guido, think are easiest to read.
The thing is, once you get rid of block start and end notation, all arguments about matching braces v. one-true-brace go away. Python is very flexible in its indenting, and the only requirement is that blocks be indented. You can indent Python the way you think is best, not the way Guido wants.
Oh, I'm still waiting for your alleged "evidence".
The fact that people don't have the problems that you insist we learned were inevitable in the 70s. You put forward a falsifiable hypothesis, and a counterexample falsifies it.
No, they have a host of new and different problems caused by the use of meaningful whitespace.
Well, that contradicts your original claim then, doesn't it? And the funny thing is, Python users don't actually have the problems you think they should have.
Correct. One of the infinitely many that a standard distribution doesn't guarantee.
This technique discriminates against everyone who has a creative spark (call it talent, madness or just plain good old "short bus") and in favour of Joe Mediocre Average who always pulls the same predictable score and will never ever exceed his limitations and achieve anything beyond what is expected from him.
That will go down as a success, then.
Congratulations, you've just learned about type 1 and type 2 errors. And if you can think of any effective way of testing for cheating that completely eliminates either of them, the world of testing would love to hear from you.
People doing statistical analysis who don't understand that a standard distribution GUARANTEES a percentage of anomalous results, frankly don't have any business having a job in their field.
People doing statistical analysis who think that a standard distribution guarantees a percentage of anomalous results don't have any business having a job in that field. An absence of anomalous results is itself anomalous, but statistically it can happen.
I would take issue with "cheating has declined about 70 percent". How do they know?
The fact that Python users don't have the problems with whitespace that FORTRAN users did. What was established in the 70s is that FORTRAN used whitespace badly, not that whitespace shouldn't be used.
BASIC is not a religion.
Oh, I think you'll find that it is. All programming languages are. But BASIC is one of those ancient religions that nobody takes seriously any more.
Then show them how to implement what they've written as a DSL in Boo...
I'll get my coat.