xmunk

Damn, this group is a bunch of real assholes.

I do indeed and I'm uncertain if their built in video players use DRM. My guess would be probably because they likely used some off the shelf video streaming library and most of those come built on top of restricted technologies.

... and yet... it lacks clear and enforced type restrictions which help with clear code contracts. It's certainly better than Javascript but the lack of runtime enforced type checking can force defensive programming in an unnecessary manner.

Your statement isn't strict type checking. It's a restricted form of type coercion. Given how common this feature is in other languages it's weird that pythonistas feel so defensive when discussing the feature. I enjoy strict type checking, but that's my opinion - it makes it a poor choice for the sorts of projects I work on but if it's good for you then enjoy!

Big if true

... (well, bigger than zero at least)

If oil is excluded the truly boss move on Canada & Mexico's part would just be to introduce a 25% export premium on those products while the tariffs are in effect.

I think I'll continue to use ad block guilt free. I support some creators directly through patreon and that's far more effective than ad revenue.

I think that ad supported video content is pretty darn convenient, but the fact that YouTube is free is a benefit to them, not to me... I don't think ad supported video content is something that we need and I'd prefer to have reasonably priced subscriptions like Nebula.

This isn't an issue, though. PHP has the same partial typing flexibility. There are ways to solve that issue and even typed PHP still allows union types including mixed which allows any types.

Considering there is typing in the code why is there no switch to enable type checking at runtime? PHP does this with a per file declare(strict_types) - why would python be unable to have either a global or per file flag to enable checks?

Please do tariff Canadian oil... fuck we need some motivation for Alberta to stop being a damn petrol state.

I recently tried out Python. I had no idea it still doesn't have runtime enforced typing...

I didn't realize that PHP was decades ahead of it.

Being public exposes them to being taken over by the administration. Going private as a non-publicly owned entity with a stewardship board would likely end up increasing their journalistic freedom. Overtime corruption would likely seep in (as it has with most news organizations) but it'd likely start out quite mission driven.

Things like takeovers and corrupt boards only happen if greed is allowed to be a driver.

It doesn't though - and that's had an obvious chilling effect on whistle-blowers.

One of the key issues is that most politicians will express support for whistle-blowing in the abstract or when exposing flaws of opposing administrations. But the administration that is likely to be damaged by whistle-blowing is the one vested with the responsibility to protect it... and that abstract support evaporates pretty fucking quickly if it's damaging your image.

Unless my memory is faulty the modern attacks on whistle-blowing mostly date back to Obama's administration. During W Bush we had the Abu Ghraib torture revelations and the whistle-blower in that case ended up receiving high praise even while causing significant damage to both W Bush and Rumsfeld.