Readit NewsWhat alternative reasons have you explored?
Added to that the opportunities for charging the various parties for "certification" are simply too good to pass up it seems.
Authorization: I do it in the database using roles, row level security and column level security. It works well and I defer everything to PostgreSQL's security controls, it feels like the right place to do it and I don't have to worry about it going out of fashion, PostgreSQL is here to stay. Anybody else who talks to the database directly is also subject to the same authorization rules, which is nice.
Introspection: this should really be disabled on production services. Only enable it for development.
N+1 problem: I don't really have a problem with N+1 because PostGraphile converts the request into an efficient query. In other cases this problem presents itself in REST too and the article proposes hoisting N+1 queries to the controller, but that's just really moving the problem around, and you can do this with GraphQL too.
The other problems, yeah sure they are present and a worry if you're running some highly visible/very loaded public API.
> In common with other on-premise servers, this terminal server was protected by firewalls and virus software, but access was not subject to Multi-Factor Authentication (MFA).
I’m sure many people in the various tribes object to the handing over of most of their sovereignty over to the USA based on the guns held to their head (and where land was retained, it often being not merely a small subset of their land, but often completely different and worse land) but their vigorous excercise of the sovereignty they retain is not a “handing over” of anything to them “based on their ethnicity”, even to the extent that there is a rearrangement of sovereign rights between the three relevant sovereigns (state, federal, and tribal) such that there is something being handed over at all.
A relevant tweet from 2016 (https://x.com/jessicamckellar/status/737299461563502595):
> Hello from your @PyCon Diversity Chair. % PyCon talks by women: (2011: 1%), (2012: 7%), (2013: 15%), (2014/15: 33%), (2016: 40%). #pycon2016
Increased diversity in communities usually comes from active outreach work. PyCon's talk selection process starts blinded.
If 300 people submit talks and 294 are men, then 98% of talks will likely be from men.
If 500 people submit talks and 394 are men, then ~79% will likely be by men.
Outreach to encourage folks to apply/join/run/etc. can make a big difference in the makeup of applicants and the makeup of the end results. Bucking the trend even during just one year can start a snowball effect that moves the needle further in future years.
The world doesn't run on merit. Who you know, whether you've been invited in to the club, and whether you feel you belong all affect where you end up. So unusually homogenous communities (which feel hard for outsiders to break into) can arise even without deliberate discrimination.
Organizations like the PSF could choose to say "let's avoid outreach work and simply accept the status quo forever", but I would much rather see the Python community become more diverse and welcoming over time.