I think that’s canonically true for Goku and Hulk

This is Lemmy.

If you want to do all that performative reddit bullshit for attention, go back there and do it. No one will stop you.

This is some text book projection. Maybe talk to a professional about it. And yeah, you probably should stay away from cartoons and kids until you get these repressed urges figured out.

woah, who the fuck is talking about kids?

Some of the oldest porn is cartoons scratched into rocks, get off your golden age of porn high horse, or get off with it if that’s your thing.

https://en.m.wikipedia.org/wiki/History_of_erotic_depictions

You literally misread that word in the tweet. it never says that.

You’ve succinctly defined the problem, and the only solution is a cultural shift away from the norm. Hopefully that shift will be peaceful, which will most likely only happen if it’s gradual.

it is, BUT, if you read between the lines of the requirements, there’s plenty of room for pragmatic atheists (in pragmatic packs/troops). It’s not perfect, but overall Scouting has absolutely embraced inclusiveness.

Imagine scrolling back in the Slack chat 50 years to find that one thing someone said about how the chip bypass worked.

That’s why the cat is smug. It knows you know this.

A repo dedicated to non-unit-test tests would be the best way to go. No need to pollute your main code repo with orders of magnitude more code and junk than the actual application.

That said, from what I understand of the exploit, it could have been avoided by having packaging and testing run in different environments (I could be wrong here, I’ve only given the explanation a cursory look). The tests modified the code that got released. Tests rightly shouldn’t be constrained by other demands (like specific versions of libraries that may be shared between the test and build steps, for example), and the deploy/build step shouldn’t have to work around whatever side effects the tests might create. Containers are easy to spin up.

Keeping them separate helps. Sure, you could do folders on the same repo, but test repos are usually huge compared to code repos (in my experience) and it’s nicer to work with a repo that keeps its focus tight.

It’s comically dumb to assume all tests are equal and should absolutely live in the same repo as the code they test, when writing tests that function multiple codebases is trivial, necessary, and ubiquitous.

It’s not uncommon to keep example bad data around for regression to run against, and I imagine that’s not the only example in a compression library, but I’d definitely consider that a level of testing above unittests, and would not include it in the main repo. Tests that verify behavior at run time, either when interacting with the user, integrating with other software or services, or after being packaged, belong elsewhere. In summary, this is lazy.

she could have not floored it into a lake, but maybe I’m the only person that doesn’t go balls out when they’re backing out of a spot.

The P in Prod stands for “It’ll be Pfine”

Xenophobia and racism.

That guy was definitely a time traveler.

It’s true, one does not simply log into Mordor.

LOL same. It’s a tricksy little wizard.

A gravid clown, a grave situation.

This post is like drinking a French Malbec after it’s been used to deglaze a burnt pan, I love it.

That sucks, but regardless of the how’s and whys, here’s to a brand new start on the next five 🍻. May the future bring you what you need, and the wisdom to recognize it when it gets here.