Skip to main content

Skydance's Discovery+ Prices Increase By Up to 20%

3 weeks 4 days ago
Discovery+ has raised prices for new subscribers, increasing its ad-free plan from $10 to $12 per month and its ad-supported plan from $6 to $7. The hike comes shortly after Paramount Skydance acquired Warner Bros. Discovery. Ars Technica reports: The new prices take effect for new subscribers immediately. Current subscribers to the streaming service, which primarily features unscripted content, like reality shows and documentaries, will receive 30 days' notice before the new prices take effect, starting with bills issued as of November 12. [...] However, a Skydance spokesperson told Ars Technica that the pricing changes were in the works before Discovery+ knew about the merger's closing date and were not planned in anticipation of a merger. The spokesperson said that Discovery+'s prices are regularly evaluated to ensure that they are in line with the content and experience that the service offers, and the new prices reflect that. Discovery+ has increased its prices three times since launching in 2012. Before today, the most recent price hike occurred in January 2025, when ad-based monthly subscriptions increased from $5 to $6, and ad-free plans went from $9 to $10.

Read more of this story at Slashdot.

BeauHD

Representative Line: A Diamond in the Rough

3 weeks 4 days ago

Mandy's co-worker recently learned about virtual inheritance in C++. It's become their new favorite button to push, and they only use virtual inheritance.

Virtual inheritance is one workaround for the "diamond problem", where you have an inheritance tree that "recombines" via multiple inheritance: when a child class has a Hapsburg-esque parentage, it's hard to decide which inherited methods are being invoked or overridden.

In C++, imagine you have class A, which gets derived into classes B and C. Class D then uses multiple inheritance to inherit from B and C. In practice, this means that D inherits from A twice, and would have two internal copies of all of A's members.

If, on the other hand, you have B and C inherit virtually (class B : public virtual A), then class D will only actually inherit a single copy of A.

If you're reading this and going, "Boy, this just sounds like another reason to avoid multiple inheritance," you're probably right. The important thing, though, is inheriting virtually impacts how your child classes will inherit. It only matters if you have child classes.

Which brings us back to Mandy's co-worker. He read somewhere that defaulting to virtual inheritance all the time was safer, so he did that all the time. All. The. Time.

Including in this case:

class SomeSpecificDerivedClass final : public virtual SomeBaseClass

The class here is marked final. It can't be inherited from. The use of virtual accomplishes nothing.

[Advertisement] BuildMaster allows you to create a self-service release management platform that allows different teams to manage their applications. Explore how!
Remy Porter