Also, in a corporate setting, if you make a call to a buddy in your building, chances are the data will be routed on your own private routers and never even hit the ISP. I'd say that was a big plus for P2P.
Not sure why you are getting up-votes for this. It isn't adding anything to the conversation other than obvious Microsoft bashing.
The Pixel Sense technology is obviously quite new, so I'm not sure how they were supposed to put it in anything eons ago.
As far as Microsoft not shipping... Well they ship more stuff than a lot of people. True that their tablet and phone offerings are not as good as the competition (yet), but that isn't through not shipping, it's through creating products that was out of touch with consumer expectations.
In the phone world, over the lifetime of the window Mobile, they've probably been quite successful. In tablets, less so, but still they have shipped numerous times over the past decade.
Microsoft didn't capitalize on Touch-based computing (a la Surface - didn't imply about pixel sense at all) when they had the chance before.
Microsoft labs has a lot of crazy cool stuff, but they don't see daylight in the hands of the consumer. There's something to be said about that.
The point is that they missed the boat, but shipped late.
"Gates's admission that he looked at the iPhone, unveiled three years ago in January 2007 and which went on sale in June that year, and thought that "Microsoft didn't aim high enough" is a startling revelation from the man who drove the company to focus on mobile." http://www.guardian.co.uk/technology/2010/feb/12/ipad-bill-g... - that says it all!
Here's my first shot at a theory of how Pixel Sense might work
There is an IR LED backlight as well as the regular white backlight. They have an additional per-pixel LCD shutter that blocks IR. The display repeatedly displays sweeping horizontal and vertical patterns on the IR blocking shutters. At the edges of the display there are a series of IR light detectors. When an object is placed on the display, some IR light will bounce off the object and be internally reflected in the plane of the panel glass. The light is received by the detectors.
Yes you are right, the instruction timings were very exact as far as I remember. The only cases where there was an option was in the case of a branch taken or not.
Heh, yeah I still remember 6502 opcodes... 4C xx xx is jmp absolute, 20 xx xx is jsr (jump subroutine) absolute, A9 xx xx is load accumulator absolute, 8D store accumulator, 60 is rts... I could go on.
Typing shit in to the hex monitor for a few years will do that :)
I loved the 6502. Around that era I programmed the SC/MP, Z80, the 8080 and the 6800. Although the Z80 was more powerful, the 6502 holds a special place in my heart as it was the first CPU I worked with and I loved the simplicity of the instruction set.
My crowning achievement was a multi-threaded kernel for a CNC punch. Since the stack was at a fixed memory address and there was no PUSHA, I had to change threads (in response to an IRQ) by sequentially pushing the registers on to the stack and then swapping the stack with a block copy. It worked! Crazy :/
I loved reading this article - thanks for posting. Awesome stuff! Makes me want to code my own circuit emulator :)
Ditto that. My first programs were in assembly on the 6502, and I'm thrilled to see it getting this attention. I'm just sorry that I don't still have the KIM-1.
I was planning on buying a KIM-1 when my dad surprised me by buying an Apple II. I didn't end up writing anything in assembly on the Apple II, though. My first assembly language was IBM-370 in college. I wish now I had started with the KIM-1, though.
How about if Adobe helped make the decision in the first place? Let's say, Adobe realized Flash is on its last legs, that Apple hate them and their engineering staff have much greater alignment with Microsoft than any other platform. Now let's say the call up Microsoft and say, hey, how about you buy us and put our engineers to work building kick ass H5 dev tools.
At the same time, Microsoft realized that like Flash, Silverlight will never achieve universal penetration, hence why developers are reluctant to use it on the web. Microsoft, seeing Adobe having similar issues and spats with Apple think, hey, what if we bought Adobe and put all the Flash engineers on H5.
I used to be highly addicted to cell phones in the '90's.
In 2005 I spent a year working overseas. When I got back I just never got around to buying a new phone. I have to say, it has been extremely liberating.
So much so that we went one further - we don't answer our land-line either unless it's someone we know and we don't check voice mail.
I also don't wear a watch and go to sleep/get up whenever my body tells me to rather than stick to a strict schedule.
You can reach me via email, MSN, GoogleTalk, Skype or hey, knock on my door and say hello!
Net neutrality is a concept founded upon a fantasy.
The idea that we should all get the same priority on the Internet is ridiculous. It has always been the case (and always will be the case), that the more money you have, the better services you can acquire.
From the guy running a gaming server, through the hacker building a highly scalable network using Linode, CNN using Akamai for streaming media and Google building hundreds of data centers; we're all willing to pay for bandwidth or reduce latency.
I'm not against the idea of network neutrality, quite the contrary; however, the gap between the aspiration and what goes on in practice is already too great. We're all players and it can never be unwound.
I agree. That's why we should keep it out of the law, since it's an unrealizable ideal, and just try to approximate it as much as we can. Egalitarianism is nice, but I don't think it's a moral imperative.
