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.

2016->2019

If you’re worried about the veracity of the claims, I can assure you they’re true.

Tabs are a dark pattern confirmed.

The war is over, long live spaces.

The north east US is dotted with high (physical) security Amazon data centers . I promise those aren’t hosting files you can search Google for, if you know what I mean.

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?

X is 36 years old. Wayland is 15. Wayland was not the first attempt at unseating that throne and for the sake of all our sanity, I hope it’s the last. I don’t want Wayland to win because it’s better, I want Wayland to win because I’m tired of trying to use it and having to go back to X because it broke something.

No.

System D was/Is a philosophical debate.

Wayland vs X is a mortal attempting to summit Mt. Everest naked. Everyone is cheering Wayland on, no one believes it’ll succeed.

Even the X people are like “Honestly it’d be a relief if you pulled this off, we’re so tired, please end us”

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

He was high on foot crust fungus, I think we can give him a pass.

why even wear a shirt at that point?!