There is no useful subset of C++ that is a) statically checkable and b) guarantees absence of dangling pointers and null dereferences.
You can build Rust programs and libraries that don't link to the standard library (as you can in C) This is very useful. Rust is pretty much the only language that lets you write complex safe code and still not link to any standard library (since its memory-safe competitors all require GC).
Your last sentence sums it up nicely. If you stick to the safe subset of Rust (which is almost the entire language, and enough to write almost all of a high-performance Web browser in, for example) then you can't trigger undefined behaviors, and references that claim to be non-null are guaranteed to really not be null. Escaping from that subset requires you to write the "unsafe" keyword.
OTOH C++ has nothing like that. It's very very easy in practice for C++ code to accidentally trigger undefined behaviors that can cause anything to happen, and there's no way to tell at compile time whether the code is safe.
int* p = nullptr;
int& p2 = *p;
C++ provides no safety guarantees: there's no subset of C++ that can be statically checked to be safe, that's rich enough for C++ programmers to use in practice. As soon as you use pointers or references you have the possibility of the underlying object dying and leaving a dangling reference.
The scenario you describe is pretty much how it worked, with Google and Netflix doing most of the forcing, and Microsoft only helping out a little bit.
So you would not have helped save the thousands of Yazidi lives that were saved last August?
FWIW Hobby Lobby always provided, and still provides, at least ten different kinds of contraceptive coverage to its employees.
That MediaMatters page --- like most other material on this subject --- is artfully designed to mislead.
Rust offers manual memory management with automatic safety checking --- the language guarantees you don't leak memory, and you can't access an object after it's freed (assuming you don't opt into unsafe code). No other mainstream language, including Ada, offers that.
Unfortunately, postal voting enables vote-buying.
MSE support isn't in Firefox 36.
The Youtube-only thing is currently being targeted for Firefox 37, and enabling it in general for 38 or 39 once the standards-compliance issues are worked out.
Half of the sample is below the _state_ average. As in, below the average of a different sample.
Ignoring average vs median issues, what this says is that folks in SV are no more likely to get their kids vaccinated than folks in CA in general are.
Even the quote Slate cherry-picked to drive their click-bait headline is innocuous. Parents *do* have a right to decide what's best for their children. That right must be balanced with public health concerns, so it makes sense to make vaccination mandatory (or mandatory-for-public-schoolers) in some cases, but surely not *all* cases as you move down the scale of public health impact. In particular there will be cases where the public interest would be served (a little) by forcing everyone to be vaccinated, but that interest doesn't outweigh the additional dilution of parental rights. That seems to be all Christie said here.
* Proper open, royalty-free standard (IETF)
* Encryption (DTLS)
* Opus CBR mode for high resistance to traffic analysis
* Standardized NAT traversal (ICE, STUN, TURN)
* Supported in Chrome and Firefox, plus other products
* Coordinate WebRTC sessions with any Web site
The funny part is, I bet HTML5Test doesn't measure what you thinks it measures...