Correct me if I'm wrong, but you should have more than two choices for your vote. Sure voting independent has it's pitfalls, but choosing not to vote will not change anything.
I thought that too, but wikipedia and other online sources say that this only applies when a defensive player is attempting to make a play on the runner. At that point the runner must proceed on the most direct path to the base, without deviating by more than 3ft, otherwise the runner is called out.
Online references aside, this makes a lot of sense thinking of the baseball that I've played and watched on tv.
And who is to decide which programmers work is better? Hey wait..
Next you'll have to have another competition between two managerial candidates to see who does a better job of judging the programmers' work.
Gimmickry is not going to solve the issues that we have in software development. You can probably only count on two hands the number of true 'one size fits all' solutions and this isn't one of them.
Seriously, how often is it the case that machines pay out *LESS* than they are meant to. We'll never know and I don't anyone in the industry is looking very hard to find out.
Code and electronics aren't perfect, but that isn't the player's fault. Perhaps players cannot be paid out in full in all cases, but the awarded prize shouldn't be miniscule.
I'd like to point out though, that just because a game has simple rules, doesn't mean it isn't very complicated to play. Look at how long it too for someone to completely 'solve' the game of checkers (using a computer).
And how does this situation differ other than the fact that the alloc/free operations are done local to the JVM instead of making system calls? The fact that the JVM is doing the work doesn't magically make memory management easier.
The other thing that I'm skeptical about is that the article seems to be contradicted by a more recent paper by the author that they are referencing (see Zorn http://portal.acm.org/citation.cfm?id=582419.582421). In the newer paper, Zorn et al. say that custom allocators are less efficient than a modern general purpose allocator.
I think that Rogers just had HTC remove the paid app functionality from the phone, and surprise surprise, Rogers has their own paid market instead (which is useless). I'm considering reinstalling the OS to turn my Dream into a regular Google phone.
For a neat visual presentation of the physics they're relying on, Mythbusters did an experiment on the explosive power of thermite powder and water vapor http://www.youtube.com/watch?v=BnHR4cMXiyM.
I don't think that's accurate, the info online indicates that cuban wasn't the sole owner of Broadcast.com (which was a company making money), and the transaction was for Yahoo stock rather than cash see http://news.cnet.com/Yahoo-completes-Broadcast.com-acquisition/2100-1023_3-228762.html/. If he's still got $2bn after the dotbomb, then that's not bad. Call the guy an idiot mouth piece, but his financial skill isn't that bad.
But one German tank could shoot down ten Russian ones. So the count alone is not the point.
Don't see the Russians short. Their tanks may not have been as technically advanced as the Germans' were, but they were designed for the terrain where the battles were taking place (snow, cold, mud pits) and they were easier to repair and manufacture. I think that if we looked at what happened in these battles, you wouldn't see the lopsided a result you're claiming.
For those of you who find the wording of the review slimy, keep in mind that almost all of the material in the book is on rand's website. Also, the book is over a year old by now, so it seems odd that it would be advertised now.
Anyway, the book is a decent read if books are your thing.
It isn't up for debate that tupple stores are a very useful tool. That being said, they aren't a silver bullet for *ALL* data storage situations. For types of data that are inherently tabular, I really doubt that 40 years of RDBMS development will be trumped by a tuple store. When you move to hierarchical data though, things are reversed.
So were the original X-Wing and Tie Fighter games. Either way, you can make a great game but at the end of the day there has to be a hook to keep you engaged. You can do this with a really compelling story or just fun game play. I just think that making it so it's harder to die doesn't really tackle the real problem i.e. hitting the sweet-spot difficulty wise, or coming up with something new or fun.
I haven't played the game, but that said, how much of the heart of great games was the thrill of just squeaking by? If you know that there isn't any way to loose, what you're left with is a empty shell. Nice to look at, and shows you some neat tricks, but nothing else later. Putting training wheels on a game isn't the future, it's just a gimmick to try and make a bland game that offends no one, and doesn't really try to solve the problem of playability. My 2c.
I believe that there's some clever tricks you can use when generating tuple keys to make things fuzzier. Not easy, but if you customize your approach and know enough about the data, it should be possible
You're right about the key space splits, there's an addon to memcached called libketama that uses consistent hashing to do exactly that.
I don't disagree, the point that I was trying to get at was that the OP's conclusion didn't jive with the site. I've never owned an SLR and I'm pretty sure the majority of the photo quality problems I've had are the fault of the person holding the camera.
The risk of cancer and the strain on your body from going through radiation is a pretty big downside. Unless there is a way to more selectively kill bone marrow, I don't know how many people would want to go for this.
I'd say that it's more of an architectural problem than anything. You can add and multiply strings with the the same operators in Python which also has weak typing.
Slashdot Mirror
Correct me if I'm wrong, but you should have more than two choices for your vote. Sure voting independent has it's pitfalls, but choosing not to vote will not change anything.
I thought that too, but wikipedia and other online sources say that this only applies when a defensive player is attempting to make a play on the runner. At that point the runner must proceed on the most direct path to the base, without deviating by more than 3ft, otherwise the runner is called out.
Online references aside, this makes a lot of sense thinking of the baseball that I've played and watched on tv.
It looks like a gladius to me http://en.wikipedia.org/wiki/Gladius
And who is to decide which programmers work is better? Hey wait..
Next you'll have to have another competition between two managerial candidates to see who does a better job of judging the programmers' work.
Gimmickry is not going to solve the issues that we have in software development. You can probably only count on two hands the number of true 'one size fits all' solutions and this isn't one of them.
Seriously, how often is it the case that machines pay out *LESS* than they are meant to. We'll never know and I don't anyone in the industry is looking very hard to find out. Code and electronics aren't perfect, but that isn't the player's fault. Perhaps players cannot be paid out in full in all cases, but the awarded prize shouldn't be miniscule.
Yes, that was the point that I was attempting to make.
I'd like to point out though, that just because a game has simple rules, doesn't mean it isn't very complicated to play. Look at how long it too for someone to completely 'solve' the game of checkers (using a computer).
And how does this situation differ other than the fact that the alloc/free operations are done local to the JVM instead of making system calls? The fact that the JVM is doing the work doesn't magically make memory management easier.
The other thing that I'm skeptical about is that the article seems to be contradicted by a more recent paper by the author that they are referencing (see Zorn http://portal.acm.org/citation.cfm?id=582419.582421). In the newer paper, Zorn et al. say that custom allocators are less efficient than a modern general purpose allocator.
I think that Rogers just had HTC remove the paid app functionality from the phone, and surprise surprise, Rogers has their own paid market instead (which is useless). I'm considering reinstalling the OS to turn my Dream into a regular Google phone.
For a neat visual presentation of the physics they're relying on, Mythbusters did an experiment on the explosive power of thermite powder and water vapor http://www.youtube.com/watch?v=BnHR4cMXiyM.
I don't think that's accurate, the info online indicates that cuban wasn't the sole owner of Broadcast.com (which was a company making money), and the transaction was for Yahoo stock rather than cash see http://news.cnet.com/Yahoo-completes-Broadcast.com-acquisition/2100-1023_3-228762.html/. If he's still got $2bn after the dotbomb, then that's not bad. Call the guy an idiot mouth piece, but his financial skill isn't that bad.
Genetically engineered whales with a built in cargo hold. You just have to train them well, and take advantage of their natural migration patterns..
Don't see the Russians short. Their tanks may not have been as technically advanced as the Germans' were, but they were designed for the terrain where the battles were taking place (snow, cold, mud pits) and they were easier to repair and manufacture. I think that if we looked at what happened in these battles, you wouldn't see the lopsided a result you're claiming.
Certainly true, but in this case practically *Every* business is the exclusive supplier.
For those of you who find the wording of the review slimy, keep in mind that almost all of the material in the book is on rand's website. Also, the book is over a year old by now, so it seems odd that it would be advertised now. Anyway, the book is a decent read if books are your thing.
It isn't up for debate that tupple stores are a very useful tool. That being said, they aren't a silver bullet for *ALL* data storage situations. For types of data that are inherently tabular, I really doubt that 40 years of RDBMS development will be trumped by a tuple store. When you move to hierarchical data though, things are reversed.
They already do through iTunes, there just aren't a ton of them yet.
Not true, I watched a review online and read the critique on Wired.
So were the original X-Wing and Tie Fighter games. Either way, you can make a great game but at the end of the day there has to be a hook to keep you engaged. You can do this with a really compelling story or just fun game play. I just think that making it so it's harder to die doesn't really tackle the real problem i.e. hitting the sweet-spot difficulty wise, or coming up with something new or fun.
I haven't played the game, but that said, how much of the heart of great games was the thrill of just squeaking by? If you know that there isn't any way to loose, what you're left with is a empty shell. Nice to look at, and shows you some neat tricks, but nothing else later. Putting training wheels on a game isn't the future, it's just a gimmick to try and make a bland game that offends no one, and doesn't really try to solve the problem of playability. My 2c.
I believe that there's some clever tricks you can use when generating tuple keys to make things fuzzier. Not easy, but if you customize your approach and know enough about the data, it should be possible
You're right about the key space splits, there's an addon to memcached called libketama that uses consistent hashing to do exactly that.
I don't disagree, the point that I was trying to get at was that the OP's conclusion didn't jive with the site. I've never owned an SLR and I'm pretty sure the majority of the photo quality problems I've had are the fault of the person holding the camera.
That isn't the conclusion that the author came to. If you compare http://www.luminous-landscape.com/images-85/h2.jpg and http://www.luminous-landscape.com/images-85/g10-comp.jpg there is definitely a different between the yellows and the depth of focus on the expensive camera is far better (compare the red leaves on the upper left).
The risk of cancer and the strain on your body from going through radiation is a pretty big downside. Unless there is a way to more selectively kill bone marrow, I don't know how many people would want to go for this.
I'd say that it's more of an architectural problem than anything. You can add and multiply strings with the the same operators in Python which also has weak typing.