I was kind of impressed by what Natal can do... but since MS is trying to keep the device less than $99 (that means that the cost of making it is probably less than $50....) with cheaper parts.... and weak chip... I am not surprised that it may be lack of power to be "lagless"
Natal uses a person as input. Of course it's much faster to press a button that inputs 'move right' than for a person to do a motion 'to the right'. This just proves what I thought all along: Mr. Burton is slow >_>
This is something that was pointed out at E3. At that time Sony's demo seemed tighter. Still while this article is flamebait it seems (nearly) everyone realizes a lot can happen in QA, so it'll be interesting to see what the final project is.
To everyone who says Microsoft will almost certainly improve the performance, ask yourself this, why would they open themselves up to all the criticism by showing a demo that they know is below the performance they will get out of the device?
Its more likely that someone said "Natal is just about there, time to show it off", and not "Natal is barely working right now, but won't the public still be wowed at what we've been doing with our millions of dollars?".
I think it's a valid question of if Natal is just too ambitious right now. Not that the tech's not there but can they do it and make it affordable?
Natal has more potential but I think it is a fair question. It's just too early for anyone to gloat about having a superior product when both were prototypes. Part of my job involves testing prototypes and half I test don't end up making the cut, but every one goes through hardware revisions. Maybe MS is banking on a better processor in the end unit with cheaper costs like they do with consoles, or maybe it'll be a another virtuaboy.
I do know that hardware engineers can't program their way out of a box, so if they wrote the demo's they were far from optimized. Molyneux's endevor was a better example of what a true programmer can do with hardware.