Perhaps you should...nothing in my post is contrary to "punctuated equillibrium" (not "punctuated evolution", BTW), which still works by random variations and selection with varying levels of reproduction success.
California is no where near as polluted as it used to be. There are many other areas of the US which are substantially worse (Houstan, Atlanta). In addition, if it were an issue of pollution, you'd see substantial differences in Southern California, where smog hangs over the city, and the San Francisco Bay Area, where the prevailing winds blow most of the smog eastward.
That's utter crap. Point me to a study that shows anything like that. There is, as yet, no concrete evidence that autism is genetic, much less a recessive trait.
The way evolution works is that there are many completely random variations and those that cause greater reproductive success are propogated.
The only way to see an "evolutionary step" (itself a misnomer) is to see some variation that causes greatly enhanced success at breeding. Needless to say, we are not seeing that here.
The number of possible moves in go has nothing to do with its difficulty.
It has everything to do with difficulty. Nearly all game playing programs use some variation on the min-max algorithm, which creates a tree of possible moves for some number of moves ahead. More possibilities per move means a larger tree, means more computation per each move of lookahead.
Unfortunately, limits on cable length prevent you from doing really cool things, like putting the DVD drive and CD burner on a rack conveniently mounted on top of the desk while the motherboard sits down, out of the way near the bottom.
It's about time. Don't get me wrong, Diablo II is a great game, but as we all know, it gets a bit s l o w in places. Now I can entertain myself playing rogue while waiting for my character to get to the other side of the screen.
Running different versions could cause really nasty problems if different versions of gcc support different levels of C (like C99 or older C) or if one version has a compiler bug that another doesn't.
Can you imagine code compiling or failing to compile randomly depending on which machine happens to compile it? Yikes! Debugging nightmare...
If your system is well designed, compiling the entire thing should be a rare event. In a well designed project, most changes occur in c files or in headers only included in a few c files, so most changes only require compiling a very few files.
Compiling the whole source tree should be the sort of thing you do fairly rarely (for a big project), perhaps once a night, perhaps automated so no one has to watch it.
If compile time is something that is a significant problem for you, you really need to look at your code design.
Banks generally aren't going to fund something so high risk. But what about the webcasters themselves? What if they went to artists, saying "We'll pay for you to record your album if you give us rights to webcast it"?
Stephen Jay Gould's last book, The Structure of Evolutionary Theory also goes into great detail on the history of evolutionary theories and the intellectual context in which Darwin worked.
It's a tough read, though, because Gould goes into excruciating detail about everything, and because it assumes a lot of knowledge in the field. Amazing book, though.
There's a lot of different sorts of barcodes. This only effects one particular type, the UPC. It is mostly for grocery type items. books, CDs and such use a different scheme (ISBN).
A lot of retailers don't use the UPC, and instead use their own item SKUs (item numbers). This requires adding a barcode sticker to all items, which can be a hassle, but it means that you control your own item numbers. This is what we did when I worked for Williams-Sonoma and Pottery Barn. We used code-128 and Symbol scanners. and had item numbers of up to ten digits.
Also, I've worked with a lot of crappy old point of sale software, and lots of crappy scanners, and I'd be surprised if any crashed on a long barcode. Mostly likely they'll just beep and refuse to scan. (Though I suppose this depends on whether they are keyboard wedge (like the CueCat, simply generating keypresses) or a more direct connection like most older registers use. Keyboard wedge systems would be more susceptible to buffer overruns, but they are definately the low-end solution. I guess I can't say for sure generally, but I know that the barcode scanning code I wrote for Williams-Sonoma definitely will not crash over thirteen digits.:-)
Slashdot Mirror
Worker bees are all closely related to the queen bee, who does breed.
Perhaps you should...nothing in my post is contrary to "punctuated equillibrium" (not "punctuated evolution", BTW), which still works by random variations and selection with varying levels of reproduction success.
But I'm WAY out of your price range.
California is no where near as polluted as it used to be. There are many other areas of the US which are substantially worse (Houstan, Atlanta). In addition, if it were an issue of pollution, you'd see substantial differences in Southern California, where smog hangs over the city, and the San Francisco Bay Area, where the prevailing winds blow most of the smog eastward.
That's utter crap. Point me to a study that shows anything like that. There is, as yet, no concrete evidence that autism is genetic, much less a recessive trait.
The way evolution works is that there are many completely random variations and those that cause greater reproductive success are propogated.
The only way to see an "evolutionary step" (itself a misnomer) is to see some variation that causes greatly enhanced success at breeding. Needless to say, we are not seeing that here.
This is also being discussed over at kuro5hin.
Unfortunately, limits on cable length prevent you from doing really cool things, like putting the DVD drive and CD burner on a rack conveniently mounted on top of the desk while the motherboard sits down, out of the way near the bottom.
It's about time. Don't get me wrong, Diablo II is a great game, but as we all know, it gets a bit s l o w in places. Now I can entertain myself playing rogue while waiting for my character to get to the other side of the screen.
If you have headers included everywhere that have to be changed often, you've got a bad design.
You'd be amazed at how often it is easy to get rid of those stupid "include everywhere" headers.
Running different versions could cause really nasty problems if different versions of gcc support different levels of C (like C99 or older C) or if one version has a compiler bug that another doesn't.
Can you imagine code compiling or failing to compile randomly depending on which machine happens to compile it? Yikes! Debugging nightmare...
If your system is well designed, compiling the entire thing should be a rare event. In a well designed project, most changes occur in c files or in headers only included in a few c files, so most changes only require compiling a very few files.
Compiling the whole source tree should be the sort of thing you do fairly rarely (for a big project), perhaps once a night, perhaps automated so no one has to watch it.
If compile time is something that is a significant problem for you, you really need to look at your code design.
Banks generally aren't going to fund something so high risk. But what about the webcasters themselves? What if they went to artists, saying "We'll pay for you to record your album if you give us rights to webcast it"?
"Slashdot! We don't suck any worse than the traditional media!"
Given that she's a piano player, that will likely make for poor reviews.
I hear tell that's important.
The way to avoid screwed up knees is to avoid cement and stick to running on blacktop, or better yet, dirt.
It's a tough read, though, because Gould goes into excruciating detail about everything, and because it assumes a lot of knowledge in the field. Amazing book, though.
How do you feel about Patenting IM Bots?
A flatscreen attached to a chair. Woo. And not even a good chair. Let me know when the mod an Aeron.
A lot of retailers don't use the UPC, and instead use their own item SKUs (item numbers). This requires adding a barcode sticker to all items, which can be a hassle, but it means that you control your own item numbers. This is what we did when I worked for Williams-Sonoma and Pottery Barn. We used code-128 and Symbol scanners. and had item numbers of up to ten digits.
Also, I've worked with a lot of crappy old point of sale software, and lots of crappy scanners, and I'd be surprised if any crashed on a long barcode. Mostly likely they'll just beep and refuse to scan. (Though I suppose this depends on whether they are keyboard wedge (like the CueCat, simply generating keypresses) or a more direct connection like most older registers use. Keyboard wedge systems would be more susceptible to buffer overruns, but they are definately the low-end solution. I guess I can't say for sure generally, but I know that the barcode scanning code I wrote for Williams-Sonoma definitely will not crash over thirteen digits. :-)
If we can't trust wild, unconfirmed rumors, what can we trust?
Wow! Apparently I can do the work of four normal programmers... time to talk to my boss about a raise!