It depends heavily on region. I personally don’t think I ever had issues with parsers. I used the awesome CV template as a base. It’s fairly simple while still not being completely boring. You can find it on GitHub or overleaf iirc (it’s been a while).
It’s my belief that it’s rare for evolution to screw up.
That’s not how it works, I’m pretty sure… Mutations will have random effects and the species evolves based on characteristics being selected for based on better survivability, reproductive effectiveness, etc.
I would do everything I could to find an alternative solution and talk them down from it.
I’ve read your other messages and it seems that you’re thoroughly convinced that this wasn’t the case here. I suggest that you get a bit more context about this whole situation, as it has been a long path of trying multiple treatments and approaches, without any success. So it’s not even remotely close to what you suggest here. No Futurama suicide chambers here.
A sex offender convicted of making more than 1,000 indecent images of children has been banned from using any “AI creating tools” for the next five years in the first known case of its kind....
I’m pretty sure that this is not true. I’d love to see sources.
There was some research before the ongoing AI-panic, focusing on hentai instead. As it is as “harmless” as the AI-generated content.
And I do recall that at the time there were voices in research making the point that the consumption of material did not have correlation with actually reducing the urges. So this seems highly unlikely.
It’s also been quite some time for me, but I have the impression that there was a plot reason for it, like the games being a war on the gods, which started with taking the place of Ares? Thus the title (but in a roundabout way)
Shared branches should always only move forward. Most Git-* systems support stuff like protected branches.
I personally like tidying up your own feature branch with rebasing and then merging it into main (preferably using only FF merges). However this is not scalable for some larger projects, and for example monorepos also make this hard to accomplish. In those cases the solution ends up being squash+merge.
The extra information about the squashed commits is usually persisted to these systems (GitHub PRs, GitLab MRs, etc) so you don’t really lose much, I guess. Although I do prefer keeping it all in plain git.
Hasn’t been the case anymore for quite some time, even though I think it has quite generous sudo rules. But yes, it’s not meant to be your main OS but instead more like a toolbox you use in liveboot/VM/etc.
LPT Do it. (mander.xyz)
Dutch woman, 29, granted euthanasia approval on grounds of mental suffering (www.theguardian.com)
A conversation with my wife (lemmy.world)
Sex offender banned from using AI tools in landmark UK case (www.theguardian.com)
A sex offender convicted of making more than 1,000 indecent images of children has been banned from using any “AI creating tools” for the next five years in the first known case of its kind....
No gods matter (i.imgur.com)
Scared the shit out of me ngl (lemmy.world)
[Julia Evans] Combining Branches (programming.dev)
source
🫄🎣 (lemmy.sdf.org)
Accurate? (lemmy.frozeninferno.xyz)