It depends on how much job experience your friend has (among other things already mentioned). It could range from around .1-.2% for a new grad to 1-2% for someone with 10+ years of experience in a more senior IC engineering role.

Thanks. He's a few years more senior than a "new grad."

Counterpoint: as a gay Californian (and a SF homeowner to boot), I strongly identify as a YIMBY.

Aside from selfishly wanting room for more local colleagues at my startup, it's my mission in life to preserve California as a refuge for persecuted LGBT people across the country. The best way to do that is to build more housing and stabilize rents, not to block sorely-needed high-density housing because there used be a historic gay bar there 50 years ago that few will remember.

3D touch isn't supported on the iPhone SE or on any iPads. Given that it's not supported across the iOS hardware line, it's not assigned any essential functionality.

I expect that it'll play a larger role after the next major redesign of iOS in a couple years.

They've started faking 3D Touch on iPads - see e.g. the new control center, which will respond mostly the same as it does on a modern iPhone if you use a similar "force touch" action (even though you're really just holding it for n milliseconds).

I'm betting on a force-sensitive iPad sooner than later, probably the next-gen iPad Pro.

Can't you just detect force, because the surface of the touch increases slightly, due to your skin being flexible? Seems like a feature you could emulate anyway.

I'd imagine that would result in a slew of false triggers, because one can slightly vary the angle or pressure of their touch without intending to invoke any kind of secondary action. One of the reasons I like the implementation of 3D Touch versus e.g. long press on Android is that it's a deliberate, positive input.

But, to the parent's point, right-clicking is never (and should never) be assigned any essential functionality. Everyone agrees that the hockey-puck mice were terrible but their initial goal was admirable, IMO - new users should always be able to find commands with a single click of a button or in a menu. More advanced users could do a secondary click for quicker access to commonly used features. That seems like a great design paradigm to follow for any alternate clicking.

Another similar rational but liberal approach would be "I want my non-homeowning friends and co-workers to continue to be able to afford the Bay Area, rather than get priced out over time."

As a young SF homeowner, that's more important to my quality of life than the price of my home going up.