nevir

Take a look at operational transforms as another great solution to this sort of problem. Many collaborative editors rely on them (Google docs, etc)

https://en.m.wikipedia.org/wiki/Operational_transformation

It's pretty difficult for anyone else to seriously enter the marketplace

Awesome! Glad you're enjoying it so far

+1 to that. The devs have also hammered out many of the core systems and are focusing a lot on balancing - which means lots of changes to watch & speculate how they'll effect the economy

If that scratches your itch, take a look at Boundless (playboundless.com). Though it's still pretty early, and the player base is tiny, the economy is pretty interesting

Good! We should be working to automate ourselves away, along with everything else. It's what we do.

Ditto taxes.

I moved to California in 2014. In 2016, I got a letter saying I owed back taxes (state) for 2012 on an estimated income. Took quite some time to clean that one up :-/

To get the real picture, though, you really also need to include total compensation (e.g. avg bonuses, shares, 401k benefits). The actual numbers are quite a bit higher, I bet. Particularly for more established companies.

> So how does one draw the lines between bad luck, reasonable security problems, everyday poor performance, civil liability, and criminal negligence?

By analyzing how they prepared for the inevitable attack (mitigation), as well as how they respond to it after the fact.

It's a chip that your motherboard manufacturer hardwired in (e.g. part of the chipset). Firmware updates need to go through the efi/bios they set up

No questions - just a huge thanks for doing this!

Vast majority have far fewer than 10 trucks.

Pretty much all the native ones. When you're debugging c/c++/etc, you're relying on source maps (via dwarf/elf/etc)

Current state of the world.

They can release a version that supports 2.7 much sooner

Your fingers don't have as far to travel, and there's no seeking involved (hand doesn't move)

The numpad is a considerably faster input method, and it can be performed one handed. For a point of sale system, this is critical: the clerk can juggle an item while typing the phone number (or price, or whatever)

Firefox (and IE) did the same thing for autocomplete=off, with the same rationale.

https://bugzilla.mozilla.org/show_bug.cgi?id=956906

Consider a future where you don't have to configure your camera before shooting, and instead do all the configuration after

It's often hard to split work between countries effectively (especially in large corporations). A lot of the larger & more impactful projects tend to be done at a home base - for political or logistical reasons.

Speaking from experience at Amazon & Google.

Yes, there's a shortage of qualified software developers, at least.

Design decisions like this are part of what makes TypeScript much more enjoyable to work in than other JS type systems (e.g. Closure, Flow).

TS tends to make pragmatic tradeoffs between sound typing, and the way JS developers tend to architect code. I'm glad they do.

Consider using conditional fields using the @include or @skip directives

Congrats to the Apollo team! A ton of work went into this

They still scan email for product features. Travel receipts for things like "my flights" & Google Now, etc

Search doesn't really need ML to be effective

Shared memory & low overhead sharing of expensive objects is probably the primary reason to use Napa

V8 doesn't support (real) forking, unfortunately

Agreed. You can be sure that whomever was involved with the bug will probably never make that mistake again.

There's also several options for purely online editing (devving on a Chromebook isn't bad)