flying_sheep @ flying_sheep @lemmy.ml

Posts

0

Comments

519

Joined

2 yr. ago

Almost as if he is one and the definitions agree for a reason.

Source?

You're talking as if there weren't pedagogic professionals who have solved this problem. If a child is that unwilling to conform even slightly, the child either has special needs and doesn't belong there, or, more likely, there's shit going down at the child's home and CPS need to get involved.

I'm thoroughly baffled that you think there's any kind of argument to be made for corporeal punishment. The scientific world has solved and moved on a century ago. The backwater sticklers who still don't get it are harmful Luddites, not people with opinions to take seriously.

Yeah, the Nazis weren't really subtle. If you instead maintain a civil front inward for public support, you can wreak havoc more effectively.

That's why fascism is a different kind of danger. It wouldn't leech off of other places for centuries, it would explosively and directly attack internal and external enemies.

Neither of these things can be risked.

Yes, that's why I wrote the part after “I see what you're getting at”

Not even slightly hidden

Fascism is a pretty specific ideology. If you want to learn more, Umberto Eco made a list.

I get where you're getting at: the role of past and ongoing colonialism is still being downplayed. But you're wrong. There are very good reasons why we should fear fascism in particular.

Wipe it off, tell the child in no uncertain terms that this is never acceptable, and if it continues being confrontational to that degree, send it to the principal's office to get detention.

… I'm just joking, I didn't attack anyone, only a multi-billion tech conglomerate. I don't understand howi can possibly be an ass here.

Cancer? Eating feces? Stabbing forks in your own eyes?

There's loads of alternatives!

No reason. It's just that when there wasn't anything to experience it, nobody asked themselves that question.

So the question is a consequence of our existence, and that's the answer

Negative rings are a horrible proprietary liability.

That's been clear from their inception, and this changes nothing.

Huh, I really like code like that. Having a multi-step process split up into sections like that is amazing to reason about actual dependencies of the individual sections. Granted, that only applies if the individual steps are kinda independently meaningful

To adapt your example to what I mean:

 Java

    
Baz do_stuff(int count, boolean cond) {
    Foo part1 = function1(count);
    Bar part2 = function2(cond);
    return function3(part1, part2);
}

  

This allows you to immediately see that part1 and part2 are independently calculated, and what goes into calculating them.

There are several benefits, e.g.:

1. if there is a problem, you can more easily narrow down where it is (e.g. if part2 calculates as expected and part1 doesn't, the problem is probably in function1, not function2 or function3). If you have to understand the whole do_stuff before you can effectively debug it, you waste time.
2. if the function needs to be optimized, you know immediately that function1 and function 2 can probably run in parallel, and even if you don't want to do that, the slow part will show up in a flame graph.

Not just all cultures, all eras as well. From Mesopotamian stone slates over medieval hogshide, paper to the internet: boomers gonna complain

dbg!() for Rust users

He works on Linux where he controls the whole stack down to the metal and I love that for him, but other people have to call library code, and them debug that if it doesn't work as they thought it would.

Unintentional incest is old, from Greek mythology.

You can theme plasma and turn the effects off. Why isn't that exactly what you want?

You can update the whole base image. Vanilla OS and SteamOS have an A/B partition that holds the currently-in-use image and can also hold a to-be-used image.

Updating works by adding the to-be-used image, setting a configuration option that tells the system to boot that one, and on the next boot it'll check if the new one is bootable, then either boot it and mark it as working, or boot into the old one and display an error about how out wasn't able to boot into the new one.

There's smart things going on like maybe hard linking files that didn't change between the two images and therefore saving space and copying time.

The result is that you never have a broken system, but you can still frequently update the base image.

I feel like that has been superseded by Nix these days. Arch is now boring stable tech.