Have you considered that due to their education and research those people may know more on the subject than you do?
Regret rates for transition remain notoriously low (within 2%) with main reasons for regret stated to be transitioning too late or environmental lack of acceptance or support.
Besides, despite some orgs claiming there is a "transgender trend", we are just not seeing this in the data.
After reading the above I don't believe they concluded stress of living in a non-accepting world is the primary reason.
30% think about killing themselves and 4%+ try each year is shocking. I think whatever side of the debate you are on we can agree things aren't working out for too many people who go through this process. If this was a drug or vaccine or hair shampoo it would have been pulled off the market.
Through what process? This was a study about trans and nonbinary people, not specifically about people who have “transitioned”
I would imagine the rate of depression and similar disorders in trans people is extremely high. To be so unsatisfied with one’s own body that you consider (or go through) major treatment and surgery to change something so fundamental.
> Genspect, which is also a biased source on the subject:
Organization that supports position <x> supports position <x>.
If Genspect can be discarded as being a biased source, then so can WPATH and every other org supporting gender ideology.
Given the fraught nature of the debate, Wikipedia seems like a poor source for determining the bias of players in the debate - the most passionate debaters have plenty of time to just edit Wikipedia.
Can you explain what „gender ideology” is supposed to mean?
The primary issue with Genspect is poor scientific rigour applied to their publications, as I have shown above. Pretty much „if it fits our platform, we will spread it”.
> *70%-80% of children who expressed transgender feelings, overtime, lost those feelings.
This number most likely comes from a study that classified girls as transgender based on behaviors like preference to wear their hair short of wear pants instead of dresses or skirt:
Media research points to transgender topic being spun primarily by traditional media and social media as a political wedge issue to mobilize right-leaning voters, akin to abortion rights before:
it's only a fallacy in purely logical arguments. Appeal to authority makes sense in medical, scientific, engineering, and other contexts when the arguments necessarily depend on ambiguous data and subjective conclusions.
I got another one from a different username right after posting this. And yes, lots of them. I wish I wasn't at work so I could check out what's on that link, lol.
If anyone is going to examine it, please post what you find.
CPython 3.13 went further with an experimental copy-and-patch JIT compiler -- a lightweight JIT that stitches together pre-compiled machine code templates instead of generating code from scratch. It's not a full optimizing JIT like V8's TurboFan or a tracing JIT like PyPy's;
Good news. Python 3.15 adapts Pypy tracing approach to JIT and there are real performance gains now:
While this is great, I expected faster CPython to eventually culminate into what YJIT for Ruby is. I'm not sure the current approaches they are trying will get the ecosystem there.
I implemented most of the tracing JIT frontend in Python 3.15, with help from Mark to clean up and fix my code. I also coordinated some of the community JIT optimizer effort in Python 3.15 (note: NOT the code generator/DSL/infra, that's Mark, Diego, Brandt and Savannah). So I think I'm able to answer this.
I can't speak for everyone on the team, but I did try the lazy basic block versioning in YJIT in a fork of CPython. The main problem is that the copy-and-patch backend we currently have in CPython is not too amenable to self-modifying machine code. This makes inter-block jumps/fallthroughs very inefficient. It can be done, it's just a little strange. Also for security reasons, we tried not to have self-modifying code in the original JIT and we're hoping to stick to that. Everything has their tradeoffs---design is hard! It's not too difficult to go from tracing to lazy basic blocks. Conceptually they're somewhat similar, as the original paper points out. The main thing we lack is the compact per-block type information that something like YJIT/Higgs has.
I guess while I'm here I might as well make the distinction:
- Tracing is the JIT frontend (region selection).
- Copy and Patch is the JIT backend (code generation).
We currently use both. PyPy uses meta-tracing. It traces the runtime itself rather than the user's code in CPython's tracing case. I did take a look at PyPy's code, and a lot of ideas in the improved JIT are actually imported from PyPy directly. So I have to thank them for their great ideas. I also talk to some of the PyPy devs.
Ending off: the team is extremely lean right now. Only 2 people were generously employed by ARM to work on this full time (thanks a lot to ARM too!). The rest of us are mostly volunteers, or have some bosses that like open source contributions and allow some free time. As for me, I'm unemployed at the moment and this is basically my passion project. I'm just happy the JIT is finally working now after spending 2-3 years of my life on it :). If you go to Savannah's website [1], the JIT is around 100% faster for toy programs like Richards, and even for big programs like tomli parsing, it's 28% faster on macOS AArch64. The JIT is very much a community effort right now.
PS: If you want to see how the work has progressed, click "all time" in that website, it's pretty cool to see (lower is faster). I have a blog explaining how we made the JIT faster here https://fidget-spinner.github.io/posts/faster-jit-plan.html.
Thank you for your contributions to the Python ecosystem. It definitely is inspiring to see Python, the language to which I owe my career and interest in tech, grow into a performant language year by year. This would not have been possible without individuals like you.
Because not everything is done as EU law. Frequently its an executive order or a directive passed down from national minister or other govt official to their branch or other branches to make their base happy at expense of people currently blamed for govt’s failures.
Eg. no law in Poland regulates legal gender change process. But there is a series of directves for courts on how this should be addressed issued by whoever is in the govt at the moment. One govt issued a directive that those are low prority, other that spouse and children should have a power to veto, another that actually those are high priority and then govt-appointed judges in the supreme court decided to veto the veto and implement new procedure altogether. And none of this is in the law - just directives for judges from pliticans and higher judges.
We are on schedule. People seem to need to get a reminder every few generations why authoritarians are terrible at running the country. Sometimes the process is peaceful. Sometimes it isn’t.
But the blame is not 100% on the authoritarians. The „we’ll refuse to do anything about your living conditions so you’ll radicalise and vote in somebody radical” is part of the cycle too.
I’m guessing this list is defined by Mac users who all got taught em dash somewhere similar or for similar reasons. It is only easy to use on a Mac. But I wonder what is the 2nd common influence of users using it?
As per the wiki article someone else listed — the compose key was available on keyboards back in the 1980s (notably it was invented only 5 years after the Space Cadet keyboard was invented!).
Some DOS applications did have support for it. The reason it wasn't included is baffling, and it's especially baffling to me that other operating systems never adopted it, simply because
compose a '
is VASTLY more user friendly to type than:
alt-+
1F600
which I have met some windows users who memorize that combo for things like the copyright symbol (which is simply:)
The compose key feels mandatory for anyone who wants to type their native langauge on an US-english layout. The combination[0] is "Compose--." though: –
As it should be. I wish this convention were present across more software, “-“ “- -“ and “- - -“ should be the UI norm for entering proper dashes in text input controls.
Though it does still require nominating a key to map to Compose. And is not generally meaningfully documented. So I’d only call it easy for the sorts of people that care enough to find it.
But then, long before I had a Compose key, in my benighted days of using Windows, I figured out such codes as Alt+0151. 0150, 0151, 0153, 0169, 0176… a surprising number of them I still remember after not having typed them in a dozen years.
In electrical engineering I'm still using a few alt codes daily, like 248 (degree sign), 234 (Omega), 230 (mu), and 241 (plus or minus). I'd love to add 0151 to the repertoire, but I don't want people to think I used AI to write stuff....
My favourite android keyboard has a compose key and also a lot of good defaults in long touch on keys (including en and em under dash). Only downside is last android update causes the keyboard to be overlapped in landscape mode. A problem with a number of alternative keyboards out there.
https://github.com/klausw/hackerskeyboard/issues/957
And whether the user cares to ‘write properly’ to boot. I love using dashes to break up sentences - but I rarely take the time to use the proper dashes, unless I’m writing professionally. I treat capitalization the same way - I rarely capitalize the first letter of a paragraph. I treat ‘rules’ like that as typographic aesthetic design conventions - optional depending on context.
I recently learned to use Option + Shift + `-` (dash) on macOS to type it and use it since then because somebody smarter than me told me that this is the correct one to use (please correct them if you know better :D).
I've been typing "—" since middle school 25 years ago. It's trivial on a mac and always has been (at least since OSX, not sure about classic). Some folks are just too narrow-minded to give others the benefit of the doubt.
Regret rates for transition remain notoriously low (within 2%) with main reasons for regret stated to be transitioning too late or environmental lack of acceptance or support.
Besides, despite some orgs claiming there is a "transgender trend", we are just not seeing this in the data.
reply