Consistency with their previous default desktop environment, Unity.

Or companies do hire security, but the security team is incompetent and unable/unwilling to adapt to new challenges. Then it devolves into security theater, until either someone new comes who cleans house or a breach happens.

Arch: I need reproducible setups. Also bleeding edge is not for me.

I have to give credit to their documentation though!

What put me off selinux is that the officially documented way of generating a new policy is to run a service unconfined, and then generating the policy from its behaviour. This is backwards on so many levels… In contrast policy-based admission control in kubernetes is a delight to use, and creating new policies is actually doable outside of a lab.

Warm Blooded Hugger.

so what are the reasons why it’s a bad daily driver?

Don’t need to go any further than “default user is root.”

Sometimes the X is not quite at the spot. My guess is that it’s under the sand too the right on the first picture (possibly underwater).

WASD = Path of Vampire Survivors?

It was Arkanoid for me.

Alley Cat, Dukem Nukem 3D, Ultima (4, 5, and 7), Daytona, Day of the Tentacle, Zack McCracken…

Using containers from public registries is no worse than using third party software. In both cases there’s a risk of malicious code. The big difference is that for containers you can scan the image before running it, SBOMs are becoming ubiquitous so dependency vulnerabilities are easier to detect, and runtime protection software is more effective on containers because each container has a deterministic expected behaviour, making it easier to find deviations. I’d much rather manage runtime controls for containers than craft selinux policies.

The bottom line (which the OP article misses) is that while individual container configurations require more effort to set up the additional work to manage them at scale is low, whereas compliance for host based installs is requiring more and more effort. In fact given how popular curl | sh ... is becoming for host based installs I’d argue that they are regressing in terms of safety and reproducibility.

That’s impossible, we know Anakin is Luke’s dad and Obi-Wan told Luke that Vader killed him.

16 and below is unambiguous. It’s a child up to and including 16 years old. Compare that to “below 17” for example, which technically means the same but might be confused to include 17 by someone skimming the question.

I don’t recall Reddit having unique content - what I do remember however was that it had aggregated content. It filled the role of Slashdot, Fark, and other sites, and it had a comment threading system that was far more usable. The memes came after.

That’s s good trick.

Legally it is quite clear. Taking a description of a closed source program and writing a new one is ok in most cases (unless that description is API docs - see Cisco vs Arista). Taking a look at closed source software and then implementing your own version is poison as far as OSS goes. OP implemented the first version, so that’s already a problem. They may get away is they describe what the program does to someone else and let them implement it, but OP would not be able to touch the source code

If you can find a Portuguese translation of Borges’ books that would be a good choice.

TL;DR: It’s Prometheus, and he didn’t call the whole film dumb, just a lot of its plot points.

Take a machine with Linux preinstalled. Will it run Linux without problems? Yeah, of course.

Take a machine with Windows preinstalled. Will it run Linux without problems? Check the list.

Many much housen.