But you've got to admin that's a damn funny phone number for them to have. And hey, I guess it works, because before I had no clue what the phone number is (don't care, because I've got good insurance through work). Now I've got it memorized and I'm sure I'll never forget it.

Actually, unlike Microsoft and Sony, all Nintendo has to do is sell the system and they've already made a profit, even on launch day.

As far as selling games goes, well let's take a look at the top selling games across all consoles

http://en.wikipedia.org/wiki/List_of_best-selling_video_games#All_Consoles

If we disregard Wii Sports (since it was included for free) and all previous generation consoles, then we have the following:
Mario Kart Wii
Wii Sports Resort (some of these were included, but some were purchases separately
Wii Play
New Super Mario Bros Wii
Grand Theft Auto: San Andreas
Wii Fit
Wii Fit Plus
GTA V

That's 5 or 6 top sellers for the Wii (depending on if you count Resort), and only 2 for the competition. Looks like they aren't hurting too bad. But what about just the overall total of all games sold for the console, worldwide?

http://www.vgchartz.com/analysis/platform_totals/Software/Global/

Wii: 901 million games
360: 826 million games
PS3: 749 million games

Yep, that is indeed an odd form of success. Most hardware sold (with none of it sold at a loss), and most games sold. What a total failure.

Oh, and since you said you didn't know the answer about the tie-ratio:
http://www.vgchartz.com/analysis/platform_totals/Tie-Ratio/Global/

Wii: 8.99
360: 10.48
PS3: 9.35

So yeah, they are on the bottom of that metric, but still very respectable...only 4% lower than the PS3 and 15% lower than the 360. Not bad at all considering all those system supposedly sitting unused on shelves.

Assuming you and the GGP are the same AC...moving the goalposts a bit now, huh? You said, when referring to the volt, that you should get 1000 mph out of THIS CONFIGURATION. Well guess what...THAT configuration has a 16kwh battery array, not 60kwh or 85kwh as the model S does. Now suddenly you are talking about adding the volt's engine to an array the size of the model S. Guess what...not you've got the inefficiencies of having to do the power conversion, plus you have the weight of the huge battery array, plus you have the weight of the ICE, plus the weight of the gas. Oh...and lets not forget about costs. Instead of a $40k or $80k car, you're added all of this expense and complexity together, so you are now probably talking about a $100k car. Yeah, I'm sure that's going to sell great, even if you could get that mythical 1000 mile range out of it.

See...again, you've moved the goalposts. The configuration we were talking about WAS a hybrid solution. That's what your 1000 mile range figure was based on...what a configuration like the volt has should get. Now you are saying "oh yeah, well hybrid IS going to suck". Well guess what....if it's not hybrid...if it's purely electric, then you DO NOT HAVE AN ICE in the car to recharge the battery. So how exactly do you "charge the batteries 3 times" without having an ICE in the car?

You're all over the place here. It seems like you just have a hatred for GM and/or the Volt and it's causing you to just start spewing garbage without even thinking about what you are saying. Let's be real here. The Volt is far from perfect, but lets have some reality in the criticisms of it, and not just go spewing garbage that makes no sense.

Wow, not sure how you get +4 with utter crap like that. You thing that setup should be sporting near 1000 miles? OK, lets see about that. Presumably, you don't think that the model S has a pathetic range, so we'll use that as a baseline for what you think a car should get. The modelS gets 230 miles off a 60kwh battery. So that means the Volts 16kwh battery should get 60 miles. So yes, the Tesla makes more efficient use of the battery. But lets get back to that 1000 mile figure. So we've got 60 miles from the included battery. That means you think it should get 940 miles from the included fuel capacity. Well, it has a 9.3 gallon tank, so apparently you think it should be getting 101 MPG? Sorry, but even the best production motorcycles don't get that high. For production cars, the best ones only get about half of that.

So I think about 500 miles would be the absolute tops you could hope for in a really efficient car with those specs. Granted that's a bit better than its actual 380 mile range, but it's a far cry from your BS 1000 mile figure. If you are throwing out fantasy numbers, why didn't you just say 5000 miles?

Why is it at all sad that, after 20 years, I've forgotten the implementation details of a specific algorithm that I've NEVER had to implement (other than as part of the learning process back then) since it's already been implemented in the standard library of just about every language or API that I've ever worked with (and that implementation has probably been done better than I could do it, because it has likely been done by someone who has studied sorting algorithms in much more detail than I ever did)? What does that have to do with forgetting how to program? I rebuilt an engine in high school, but I don't remember how to do it now. Does that mean I've forgotten how to repair my car, too?

And how does it work? Well, I could tell you now, since the curious part of me went and looked it up on wikipedia to refresh my memory the second I finished making that post. And you might think that's fine, since that proves I can actually do it, except for the fact that, had I first ran into Jane Q. Public in an interview rather than on slashdot, I would have failed that requirement at the time.

But to answer your question with the knowledge I had at that time, the only part of it I could remember is that divide and conquer is part of it. But I couldn't remember how it dealt with getting values sorted between the left and right halves (doing a rough sort before dividing), nor anything about the pivot point or how to select it.

I'm sad to learn that, by your standards, I'm not currently a programmer, but merely a hack just out of high school, as I couldn't write a quicksort to save my life. Ironically, though, 20 years ago, when I WAS just out of high school (and WAY less experienced/skilled), I apparently was a programmer back then because I could and did write a quicksort at that time.

Or, maybe you're just really bad at expressing yourself.

Why should nobody intend to do it? I do it from time to time, and I intend it. If the subject I'm capturing is naturally vertical, and I don't intend to view it full screen on an HDTV, why should I waste all that space and resolution capturing stuff I don't care about on each side? I'll shoot it portrait and capture the subject that I am actually interested in with as much detail as possible.

Then you end up with a much lower resolution, which is very undesirable.

But to use a square sensor, you give up a lot of resolution. A lens is circular. People generally prefer photos that are rectangular rather than square. Well, for a given circle diameter, you can fit a wider 2:3 rectangle in it than you can a sqaure. That means for a given lens size, your 2:3 sensor will capture more detail than a square sensor which you crop down.

Because it would be sensor space that would rarely be used. It's not that common that people would hold in portrait but intend to shoot in landscape. And then on top of that, I don't know that it is technically possible to manufacture a plus-shaped sensor. If not, then that would mean either there would be a lot of the sensor that is completely unused (which means wasted cost of manufacturing, and possibly wasted battery life if it's not possible to keep portions of the sensor powered down), or you'd have to shrink the square sensor down to fit inside the circular lens (which means your effective sensor would be lower resolution). Neither of those are ideal trade-offs for somethings that might be used 5% of the time.

A violent assault sure seems a hell of a lot harder to me than simply following someone around and wait until they touch something you can pull a print from without the person even realizing it.

But it's not problem free. So you have class X, which implements interfaces A and B. Interface A has function Foo, so class X implements function Foo. Everything is fine and dandy. Now it's the future. Interface B has been upgraded to also have function Foo, and given a default method so as not to break existing code. If you recompile it, as you said, it will work just fine since you've got an implemented method, thus no conflict. So now you pass an object of X to a function called DoSomethingWithB that expects a B object as a parameter. In the upgraded library, that method takes advantage of the fact that B objects now have a Foo function, so it calls it. Except that the implementation of Foo in X that gets called is one that was designed to only deal with calls intended for objects of type A. Unless A.Foo and B.Foo have the same intended purpose, it's gonna fail until class X is upgraded to deal with the new B.Foo. And like I said, how does the code even know if the caller is trying to call Foo on an A or a B object? That's important because, if the purpose is different and the naming similarity is just coincidence, then you are going to need to do different things in each case.

So, first of all, that means that default methods doesn't 100% fix the problem it was intended to fix. Namely that existing code would break if new methods were later added to interfaces, as that existing code would not have an implementation. It's still possible that adding new methods to an interface could break existing code, but probably a lot less likely. I assume they'll take care in future releases to make sure they don't modify existing interfaces in such a way as to break anything using the standard library, but that may not hold true if you use any code libraries from a 3rd party.

The other thing is, I don't see how this is a whole lot different from just allowing multiple inheritance but requiring the derived class to override to resolve the ambiguity up front (rather than the C++ method of letting the caller resolve the ambiguity). And I'm actually curious how Java will allow this to be resolved in the derived class. If you implement interfaces A and B, which are completely different from each other and both implement method Foo for completely different purposes, then using the C++ method, it's easy to call object.A::Foo when you are trying to treat the object as an A, and likewise for B. But with java, will the overridden function C.Foo be able to know when the caller was treating the object as an A vs a B? If not, then it's sort of difficult for the class to know how to properly resolve these sorts of conflicts.

So java now supports default methods for interfaces? In other words "we now support multiple inheritance". Or at least that's pretty close to it. I thought the logic was that multiple inheritance is messy when you have diamond shaped inheritance, or two parent classes that have the same method names, so java only did single inheritance, but then allowed you to do interfaces to sort of simulate multiple inheritance (except you had to write all the code). But with this change, it seems the same as multiple inheritance, with the exception that interfaces cannot include (non-static) variables, only methods. Am I correct here, or am I overlooking something?

You misspelled Yellowstone

For a moment, I wanted to tell you I think you are totally wrong, but then I remembered...I'm only up to episode 3 so far. Up to this point, it seems like a really good show, to me at least. Hopefully I don't agree with you once I'm caught up, but unfortunately I could see you being right. The show reminds me quite a bit of Jericho. I loved that show initially. I loved how it showed people being isolated and falling back to low tech, and how the people come together to survive the emergency. That was really nicely done, but then they worked in the conspiracy theory part and made that a bigger and bigger part of Jericho. That really ruined the show for me. I would have been happier if Jericho left it as a mystery how everything happend.

So far (after 3 episodes), the conspiracy theory in Under the Dome is sort of small. I'm praying it doesn't take over this show too.

Although I haven't yet researched the answer online, I wish Android would provide a little better explanation of just how the backup feature works. I've got an android tablet and an android phone. I've installed different software on each one. I'm unclear on how the backup/restore works with multiple devices. When restoring to a brand new device, does it prompt you as to which old device's backup you want to restore from?