That's great news for OP.

PS: The correct link is http://www.tobii.com/en/assist...

I don't think this exists, but I could see it working:

1. Take existing eye-tracking technologies. (I'm not familiar with any but I know they exist)
2. Put up a virtual keyboard in front of your sister-in-law.
3. Track what letters her eyes trace over.
4. Use statistical analysis to guess which words they are trying to spell (like Swipe/Android keyboard).

This should allow her to spell words fairly quickly, although swipe keyboards can be frustrating at times.

+1000

Our biggest problem is letting political correctness get in the way of moral clarity. These people are trying to kill us. The more of them we eliminate or delegitimize, the better.

Most people don't need NoSQL. Last I checked, most people aren't Facebook or Google. And ironically those two companies are lining up behind http://en.wikipedia.org/wiki/N...

ACID is here to stay. We will see conventional databases improve in the latency space and NoSQL will (mostly) go away.

Impossible.

The entire premise behind NoSQL is trading consistency for availability (which actually means "latency" since everything is eventually available). You will never ever get ACID from NoSQL databases.

It's as beneficial as sailing on top of a rock. No carbon footprint there either!

Aside from the technical advantages that people keep on bringing up, one of the main non-technical advantages that Thunderbolt has is its certification process. Any USB chipset that is faster than USB2's theoretical speed is certified as USB3, whereas in order to get certified as Thunderbolt 1 or 2 you must actually reach the advertised speed.

When you buy a USB device (unless it's from a reputable manufacturer such as Intel), its actual speed is usually an order of magnitude worse than the advertised speed. That is a huge difference!

1. "code works": Easy to say, hard to check. It might work today in some circumstances but fail tomorrow in other circumstances.
2. "is maintainable": That's a subjective criteria which is impossible to enforce.
3. "is to spec": Again, easy to check for common pathways, but hard to catch all the nuances (for the same reason that no one has 100% code coverage in their unit tests).
4. "passing a security audit": This helps, but as well all know by now it does not guarantee that the code is secure. Code usually depends on 100s of transitive dependencies. No one in their right mind includes transitive code in their security audits, unless you're the military and have that kind of money.

I'm not saying that building a house is any easier. I'd simply point out that we evaluate houses and bridges after a 30-year track record. If bad things happen, people get sued and there is some form of liability.

How many people behind software development (from the programmers up to the project managers) are liable for their work 30 years later?

Until we become liable for our work there will be no incentive to measure and improve some of these metrics. Just my 2 cents.

No. It does not.

The Christian ethnically cleansed the region of Jews, then the Arabs came and did the same. The Arabs of 1946 are not natives of the region by any stretch of the imagination. They did the same in Egypt. Hint: Today's Egyptians have nothing to do with Egypt's native population from a thousand years ago. They are just Arab colonists who invaded the area and ethnically cleansed it of non-Muslims.

You might want place the blame where it's due. Arab leaders have repeatedly instructed their people to abstain during votes. You can't have representation in government if your people refuse to vote for you :)

Bullshit. References?

Give it a rest, will you?

Arabs have a strong representation in the Knesset (parliament) and a higher standard of living than Arabs living anywhere else in the Middle-East. Not to mention the various other minorities in Israel which are literally being slaughtered in the surrounding Arab countries but finding refuge in Israel.

If the government really wanted to assert control, it could use tanks, jets, nukes and many other weapons which you don't have access to. Syria is a prime example of why arming everyone does not guarantee anything.

Canada is a second example that arming everyone is both unnecessary and needlessly increases gun-related deaths.

Yes. I would recommend starting your development with Java 8. Any compatibility problems you run into will likely go away within the month as more libraries add Java 8 support. Most of them already work fine out of the box. Some of them depend on bytecode internals (e.g. the ASM library) so it'll take them a bit longer to run properly under Java 8.

That didn't really work all that well in WW2, did it? :)

Guess what? Not all wars are created equal. Some wars are good to get involved in, and others are bad.