Readit Newsno different to having your javascript decryption routines done by a website
Nonetheless you're absolutely correct; i would prefer firefox to chrome.
Dead Comment
Outside the workplace, it's rarely used for personal messages anymore. It's limited to confirmation messages, promotional mailings, forgot password links and that's about it.
The days of email are over. Everything moved into silos like WhatsApp because they offer instant responses email could never offer and a nicer UI.
Mind you, nobody has ever introduced me to a friend via social media.
Meanwhile, SMS is still going strong. Who needs an app?
"Courtney (one of the karsidhins) is an Egyptian Goddess"
"How Much Porn is Too Much Porn"
"Is this the Big L for Drake"
I just cannot imagine caring about any of this stuff, and it uses a lot of data to just load the previews. It's so annoying I did my first Instagram story this week.
Good to see snapchat is putting together some content that you wouldn't see in a tabloid magazine. I realize I probably sound like an old man, which I am not.
Unrelated, but it's astounding how well that name communicates despite being terribly spelled.
Unless you're working on research, it's hard to buy physical proximity reducing throughput; just latency.
This is why I no longer read the verge. Important to separate opinion from facts.
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.
2. It only takes freeing a tree with a few thousand nodes for it to become an issue. It happens in C++, too (heck, there've been cases where chained destructor calls overflowed the stack [1]). The reason why you don't hear more about it is because pause times just aren't that big a deal for most applications. In forum debates, people always discuss triple A video games and OS kernels and such, but in practice, only a minority of programmers actually have to deal with something even approaching hard real time requirements. Generally, most applications optimize more for throughput rather than pause times.
3. Yes, and it can be a problem for C/C++, too. It's rare, but not non-existent. Note that pools can actually make fragmentation worse for long-running processes.
4. Weak references work if you get them right. But for long-running processes, even a single error can accumulate over time.
> On the GC side, it seems like you typically get bursty, unpredictable performance, in both time and memory. Modern GCs work very hard to keep collection pauses as short as possible, but almost inevitably that means keeping garbage around for longer, which means using a lot of memory.
This ... is not at all how garbage collectors work, especially where real time is concerned. Not even remotely. I recommend "The Garbage Collection Handbook" (the 2011 edition) for a better overview. And ultra-low pause times are generally more of an opt-in feature, because they're rarely needed.
[1] E.g. Herb Sutter's talk at C++Con 2016: https://www.youtube.com/watch?v=JfmTagWcqoE&t=16m23s