Okay, but the Jews were already being regularly persecuted for actual millennia at that point, and this was in... the 1930s, with a very different geopolitical situation. On the other hand, I doubt GP has any real reason to fear imminent ethnic persecution. We can and should take our best guess as to the likelihood of catastrophic events into account in our cost/benefit analysis, surely?
The laws of gravity are entirely symmetric, so it doesn't seem fair to attribute it specifically to the sun; also, the energy in this case is coming out of the "v" in earth's good old 0.5mv^2 kinetic energy relative to the sun.
I don't think "smol pp" is meant to be unfriendly to women, but it's telling that men are expected to self-police such utterly innocuous jokes when women are present even though you couldn't find a phrase less applicable to women if you tried.
As far as I remember this disclaimer has only been on /b/, but yes, I love the turn of phrase. I think I used it in conversation within the last day or two, even.
Exactly which platforms will penalise namedropping Hitler varies and it varies by circumstances, but this is a real thing as far as I can tell, on tiktok and also on YouTube videos algorithmically flagged as "intended for children" (regardless of whether they are or not).
But this doesn't prevent SQL injection, does it? It adds a grammar feature that you can then use to build SQL injection prevention following a novel idiom. Someone still needs to write the actual SQL building logic somewhere!
I don't think this is the right idiom for doing this. Frankly I don't think SQL query generation should look like string templating at all!
The sell seems to be "now you can write code that looks like an SQL injection vulnerability, without it actually being vulnerable!". I'd rather write code that isn't a vulnerability, and doesn't look like one, and doesn't have to bend the language grammar either.
It's a pattern moreso than this specific feature. There's an important qualitative distinction for me between something that's on the level of a library (even if it's the stdlib) on the one hand and first class features (ie things that require parser level support) on the other.
Python has historically been very conservative about this but in recent years has had one controversial language extension after another, while parts of the language that actually need love are left to languish IMO.
I wanna be very clear that this is me changing my mind -- I was (still am) very on board with the highly controversial assignment expressions ("walrus operator") for instance.
I don't have much faith about what the Python language will look like if you project the current rate of changes forward 10, 15, 20 years. It really doesn't help that I consider this new thing an active antifeature.
I really was on the side of being generally willing to accept new python features, but this is getting ridiculous. What an utterly pointless thing to bloat the language with. At this point my moving to clojure as my first line language of choice is only accelerating.
This is of the category "things I wouldn't want to use even for the specific hyper niche things they're intended for". What even does a "t-string" represent? Because it's clearly not a string of any kind, it's a weird kind of function call notation. The programmer sees something that looks like string formatting, but the program executes some arbitrary procedure that might not return a string whatsoever.