throwaway91111

One note, in video games allocations are a major source of slowdown; don't allocate in your inner loop! Use object pools and arena allocators.

Sure, but presumably if you're worried about it you can sideload your own version.

Nonetheless you're absolutely correct; i would prefer firefox to chrome.

What are you imagining the hayday of email to have been like? It sounds like you're describing AIM in the 90s, or SMS in the early 00's. Before that there was IRC if you wanted realtime responses. Email has always been async.

Mind you, nobody has ever introduced me to a friend via social media.

Meanwhile, SMS is still going strong. Who needs an app?

Yea, but this enables things like e2e encryption without losing a search index.

> karsidhins

Unrelated, but it's astounding how well that name communicates despite being terribly spelled.

Thank god most code requires no innovation at all, and thank god i am the one automating others out of the job!

Unless you're working on research, it's hard to buy physical proximity reducing throughput; just latency.

True, but I am highly skeptical most people will have issues producing this level of innovation from a coffee shop.

This is why you finally give up on the verge? What would you refer to the memo as: a cool-headed rational argument? I don't even think the engineer understood what he was arguing for; misogyny isn't hard to see, regardless of the intentions.

The weirdest and most uncomfortable part is that he cares enough to alienate his employees, but not enough to encourage productive discussion. It seems like bitterness and resentment towards women.

While I understand why you might not like the phrasing, it speaks deeply about you that this is the one of thousands of verge factual errors you choose to criticize.

It doesn't.

Exactly. How is the profiling experience?

Thankfully the vast majority of work has nothing to do with innovation.

I'd love to hear your argument for "progress", whatever that is.

Agreed, but it still had the secure enclave with touch id.

Well, multicore isn't going away; concurrency (if not parallelism) is necessary for responsive UIs.

Did you have any specific improvements? The big requirements for distributed programming are mostly protobuf serialization and tcp/http; swift has both already.

How does ARC hold up for long-lived servers? Are the leaks manageable?