My kids started getting into one piece, an Anime I admittedly never watched, so I watch it with them. I get the hype now, there have been several times we’ve torn through 8+ episodes in one sitting. Skip Intro makes it fly by.

There are so many Java libraries that I would probably set on fire if they were physically tangible in any way.

depends on how cheap the farm was being when they bought insurance

In the U.S., you can build rockets all day long, they cannot be guided.

https://www.law.cornell.edu/uscode/text/18/2332g

You’d have to convince the feds it was never designed to be a weapon. Good luck with that.

Tabs are a dark pattern confirmed.

The war is over, long live spaces.

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.

I see a dark room of shady, hoody-wearing, code-projected-on-their-faces, typing-on-two-keyboards-at-once 90’s movie style hackers. The tables are littered with empty energy drink cans and empty pill bottles.

A man walks in. Smoking a thin cigarette, covered in tattoos and dressed in the flashiest interpretation of “Yakuza Gangster” imaginable, he grunts with disgust and mutters something in Japanese as he throws the cigarette to the floor, grinding it into the carpet with his thousand dollar shoes.

Flipping on the lights with an angry flourish, he yells at the room to gather for standup.

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.

like, even bash, cat, ls, etc?

😬

That’s a deep reference. Real deep.

on osx it is 😆

I don’t like it, but I like it more than the old way of holding the button down to get to the menu. I do hate that the “see all” menu doesn’t just expand the current menu, it takes you to the old menu. There’s definitely hints of windows95 creeping into Android.

Dead people accounts.

In a similar vein, not Rob Schneider the actor, but that racist stereotype Mexican he plays in a bunch of movies. I would find it hilarious in a “I’m the dude playing the dude disguised as another dude” way.

Wait.

RDJ playing Rob Schneider playing that character.

It’s all hosted on pornhub now.

I’ve got a friend with potato feet who wears buckets for shoes. Keen is his go-to.

2600 vibe.

Windows Subsystem for Linux! (I’m kidding, go Manjaro!)

I think that was an attempt to call me out for giving zero fucks about Android spellcheck dicking with my comment.