DaveMebs

They didn’t pull out in WA, they just stopped offering really cheap plans that were easy to cancel. They continued to offer higher-end LTC Insurance.

If the manager doesn't support a reasonable amount of vacation time, then there are almost certainly other issues. It is hard for me to fathom the intersection of "good manager" and "doesn't support vacation time" not being NULL. If someone is in this situation, they should vote with their feet - the manager clearly doesn't have their best interests at heart, and this will impact them on multiple dimensions.

You think it is highly unlikely that Facebook/Meta is selling granular user data?

Requirements: Live streaming uses Apple’s HTTP Live Streaming (HLS) technology. HLS requires an iPhone, iPad, or iPod touch with Safari on iOS 7.0 or later, a Mac with Safari 6.0.5 or later on OS X v10.8.5 or later, or a PC with Microsoft Edge on Windows 10. Streaming via Apple TV requires an Apple TV (2nd or 3rd generation) with software 6.2 or later or an Apple TV (4th generation).

I don't see taxes listed as a line item in the comparison, which is a huge factor. WA State does not have income tax.

80% of hops in America come from the Yakima Valley, which is in Eastern Washington. They even have a large hop festival every year. I think this presence influences the beer scene dramatically.

If you can establish self-sustaining societies on multiple planets you eliminate humanity's greatest threat - the fact that Earth is a single point of failure.

If you take the Ballard Connector to MSFT it is not that bad. 45-60 minutes depending on traffic. With the new 520 work on the Eastside, the carpool lanes are speeding things up dramatically and I expect it's closer to 45 most days (I'm in Phinney currently, and I'm usually at 45-50 minutes on the last stop).

But if the DRM solution is implemented through JS code in the browser, it is trivial to pirate. I know DRM is always broken, etc., but at the same time it is hard to take an argument at face value that discounts the security differences between these approaches.

JS is trivial for anyone moderately skilled to crack - you're sending content in the clear from the browser through the stack.

DRM solutions enabled by EME can be much more robust and difficult to crack.

Similar to other commentators, I struggle with the issue, but just saying "put it in JS" is not a very compelling argument. The current EME approach of a publically defined API that any DRM solution can plug into feels like a pretty reasonable compromise here.

Please read the article before posting. The author specifically discusses the fact that astronauts show signs of aging more rapidly despite the fact that small doses of radiation can be good for your health.

These are site-specific implementation issues, and have nothing to do with the DASH ISO standard.

DASH is purely an XML format for describing server-side content. The issues you are describing have nothing to do with DASH and are due to implementation decisions in both the JS player and the underlying MSE object.