drobertduke

It's worth it just for copy-on-select. Auto-complete and mouseless copy are great also.

In California we have this absurd voter-approved law we call Proposition 13, which caps property rates. It effectively eliminates the only "wealth tax" we have, leaving our schools perineally underfunded and removing incentives to upzoning from both city governments and home-owners! It's a real piece of work.

Yes, Bitcoin seems to be stuck: true believers won't accept supply variability, but price stabilization (and with it, wider acceptance) is impossible without it. However it seems likely that an alternative could use some kind of internal mechanism that would effectively regulate supply without being "gameable".

The "Elite: Dangerous" example is interesting. What's the difference between flying around in space and flying around a typical FPS game? I don't have personal experience with the Rift but here are some thoughts:

- The "context" of the cockpit is helpful in some way, it's an environment which "agrees" with your inner-ear sense. If the cockpit were removed from Elite, would "presence" be lost? If a cockpit of some kind were added to a typical FPS game, would that decrease the dissociated-motion effect?

- Movement is different in Elite. The environment that disagrees with your inner-ear (space and the things in it) is far away, moves more smoothly than a typical FPS, and is sparse. This probably makes it easier to accept than the fast, jerky movement inside small, constrained environments of a typical FPS.

Great article. I think part of the difficultly with the word "guys" in particular is that it depends on the usage. Saying "hey guys" or "you guys" when referring to mixed company is generally interpreted as gender neutral. But talking about "ops guys" or "a guy" is definitely not gender neutral.

Hey everyone, one of the authors here. Myself and the rest of the Tools and Frameworks team at Box are available to answer any questions or respond to feedback.

Palo Alto, CA - Box.net

We are building the next generation of enterprise collaboration software and growing quickly. Hiring all positions.

http://box.net/company/careers/ http://www.crunchbase.com/company/box-net

A hundred people out of how many beta testers? 10,000? That would be outrageous.

There are obviously a lot of legitimate safety questions about robot cars. Are they better or worse at avoiding pedestrian collisions than a good driver? An average driver? How does the average severity of an accident vary between human drivers and robots? It will take some expensive testing and stats/actuarial work to sort out whether they would actually save lives at this point or anytime soon.

There are some important security questions too. How many exploits will be found per year? Will they be used to commit anonymous acts of violence? Do the cars connect to a network of any kind and pass viruses? If a car has been off or out of range during an infection, does it have to be quarantined from other cars and forced to update? "Pulling over to restart driving-service." How do you verify that an infected car has actually updated? Lots of completely untested, life-critical systems.

When other vendors enter the market, what kind of standards will they have to meet? How do we verify the security of their car software, will we require they be open source? If a vendor goes out of business, who is responsible for maintaining their upgrade distribution network?

There's a lot of important policies to decide on, it's going to take awhile.