Could you share some examples?

Even adjusted for maternity and career entry/exit differences, the gender pay gap is still big and real. And while there is overlap and outliers, many more women-dominated industries are at lower pay segments (and with fewer benefits) than industries dominated by men.

Before the removal of the GIL in recent years, Python seemed well-positioned to leverage the GIL to offer safe thread-cancellation points that didn’t leave interpreter internals in a corrupted state.

That’s not necessarily an endorsement of the idea of Thread.stop in many cases, since stopped user code can cause broken assumptions at a high level no matter what, but it has its uses. Erlang’s exit/2 is proof of that, though it is a very sharp and rarely-appropriate tool.

That said, Ubuntu in large production fleets isn't too bad. Sure, other distros are better, but Ubuntu's perfectly serviceable in that role. It needs talented SRE staff making sure automation, release engineering, monitoring, and de/provisioning behave well, but that's true of any you-run-the-underlying-VM large cloud deployment.

Comments URL: https://news.ycombinator.com/item?id=47619995

Points: 1

# Comments: 0

Which recent foreign policy actions by Russia indicate that they care overmuch about soft power, or consider its loss to be a significant risk?

That's not to say it's inherently necessary for it to be a third-party package (Go, Ruby, and Java are counterexamples). But this isn't a proliferation/anemic stdlib issue.

Package manager ecosystems are highly centralized. npm.org could require MFA (or rate limit, or email verification, or whatever) and most packagers would gripe but go along with this. A minority would look for npm competitors that didn't have this requirement, and another minority would hack/automate MFA and remove the added security, but the majority of folks would benefit from a centralized requirement of this sort.

(Moved from wrong sub)

That said, I'm sorry this is being downvoted: it's unhappily observing facts, not arguing for a different security response. I know that's toeing the rules line, but I think it's important to observe.

More strangely (to me), this is often addressed by adding loads of fallible/partial caching (in e.g. CICD or deployment infrastructure) for package managers rather than building and publishing temporary/per-user/per-feature ephemeral packages for dev/testing to an internal registry. Since the latter's usually less complex and more reliable, it's odd that it's so rarely practiced.

I hate that/wish it weren't so, but I think the last ~15y of M$ decisionmaking makes a lot of sense in that context.

Maybe, but I somewhat doubt it, for a few reasons:

- Kids like iPads for gaming/video watching, and the overhead of computer interfaces for them might discourage laptopping (understandable for littler kids; regrettable loss of tech familiarity for older ones, but true regardless).

- Parents/rough users like iPads 'cuz there aren't moving parts or gaps to get hammered and damaged, though the screen is a risk.

- Cellular iPads/huge phone-alikes are pretty popular, and the vast majority of users are unfamiliar with the idea of hooking a computer-shaped device up to cellular internet.

- iPads are easier to MDM-manage/lock down. You can do that on MacOS too, of course, but a lot of folks find it easier to regulate kid/employee/etc. use of an iPad because the management system is familiar and simpler.

- iPads feel like a big phone. That's a pretty intuitive switch for a lot of folks who either don't have keyboarded computers at all, or associate them with non-fun (work/school) computing. Silly distinction to draw, to be sure, but very significant in the minds of many users. The single-brick/touch aspect of iPads is desirable enough that a fold-out laptop isn't going to overlap with a lot of those users.

I think Valve’s play isn’t to steal tons of Microsoft’s gaming market share; their play is to just get enough of a market that game developers are incentivized to code to the APIs that work well in Proton, not whatever the latest and greatest in Windows is. If we cross that inflection point, Microsoft’s PC gaming chokehold will be on life support.