Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)N
Posts
1
Comments
481
Joined
3 yr. ago

  • Threads like that explain a lot about the state of the world.

  • I heard you like to irradiate things, so I put a nuke in your nuke, so you can irradiate while you irradiate.

    A project Pluto powered missile really would be the ultimate 'screw you', it could fly around enemy territory for days or more, spewing radioactive exhaust, launching warheads as it went, before finally hitting a target. Shoot it down and you have a nuclear mess, don't and you have a wider nuclear mess.

  • it's just the B-52 but the bomb bay doors may fall off during flight.

    Cunning. Extra munitions built into the airframe and deployable with minimal manual intervention. We'll take 50.

  • My god, is systemd ever a piece of crap. Coupled with ‘consistent[ha!] naming’ it’s the single most likely thing to cause a field engineer to scream into the partially-lit datacenter in abject rage and hate. Even more if they remember how fucking sysVinit actually delivered on the promise. Even more if they still remember how well inittab Just Worked.

    I agree with everything you've said, but this paragraph in particular resonated. We used to have a clean, simple, and predictable, system. Now we have exciting race conditions, a massively over complicated monolith ("but it's not", I hear the Lennart's fans scream, "you can just install the bits you want". To them I say "Try it. You'll soon wish for the sweet release of death. Install a good init system instead"), and once simple tasks being swamped by poorly designed tooling.

    I'd say the entire design of it is badly thought out, but that implies there was much though given to it's design at all. It seems more like it simply coagulated. As another commenter said, it's become popular because it makes the disto builders' lives easier, not because it's better, and that leaves everyone actually using the thing in the lurch.

  • I won't say a bad word about Gentoo, I enjoyed running it, but if you want to use sysvinit, Debian works fine with it. There's a page on the wiki (linked form the install guide) on how to do it here. I've not run into any issues over the time I've been running like this, and having a clean init system makes my day a lot better.

  • Nagios. It does depend on what you mean by monitor though. Nagios is good at telling you that "service A on host B" is down" but less useful for looking at things like performance trends. I particularly like being able to setup dependencies between services, so I get the alert for the root cause, and not all of the services that have gone down because of it.

  • You dismiss the data you recorded because it doesn't seem to support your hypothysis tgat there is greater lag in wayland, but that's not really the right approach, and I think it points to a different conclusion.

    You recorded a lag of 5 or 6 frames at 90 frames per second in both Xorg and wayland, which suggests that the lag is the same to within 0.011 seconds, and I don't think that you can say that's a huge difference. However, what you didn't test is the acceleration curve on mouse movement. If that curve is different under wayland it could easily feel infuriatingly laggy without actually showing any extra delay on the movement starting or ending.

    I'm not sure how you'd accurately test that, a HID device just sending mouse move events wouldn't do it as wouldn't mimic you accelerating the mouse from stationary, so wouldn't exercise the acceleration curve in wayland. You might need a physical device that moves your actual mouse a fixed dustance and then measure the distance the cursor moves on screen. Repeat for different movement speeds and you might have sone useful data.

  • That's not the only way to do it. In quite a lot of situations you can, instead, generate artificial data that is statistically similar to the original data set and use that instead. That works well for things like system testing, performance tuning and integration testing. Done right, you can even still pull out useful corelations without risking deanonymising the data.

  • ... and half the country is extremely enthusiastic about that.

    There's the reason nothing is done about it. It's probably not actually half, but enough people didn't speak up early enough, and so this has become the loudest voice in the room. Unless, and until that changes, the whole world is in for a rough ride.

  • Well obviously. I mean, have you ever tried eating those things without sauce? They're bland, dry, and uninteresting. Clearly that crow has a more refined palette than that.

    It probably also helps lubricate it to make it easier to swallow, crows really are smart.

  • It is genuinely difficult to tell if the stories they link to are real or just hyperbolic parody. Even just skimming them I can feel the incoherent rage and desperate glee for vengeance billowing off of them. Anyone actually reading them seriously would inevitably end up getting swept along, and it makes a lot of what we've seen make a lot more sense.

  • That's why there are all those "keep off the grass" signs. If people just walked all over the grass willy-nilly we'd soon be knee deep in benches and bins, and nobody wants that.

  • Good grief! You can't just go posting that sort of thing in public, at least tag it NSFW.

    Now please excuse me while I go and clutch my pearls in horror.

  • The problem with releasing them on day one is that you then can't gather more. If you've only just exposed the edges of the malfeasance you need time to get the rest before exposing it. Go too early and the rest of the evidence can be destroyed, covered up or those holding it coearsed into silence.

    Having a dead man's switch is a way to ensure whatever you've gathered gets released if you're no longer in a position to gather more. As such I disagree with the poster about making it public knowledge before release. Keep it secret until you have everything, then release it.

  • I'm sure he was, or at least making the statement in a wry way. It's a very English sort of humour to understate the seriousness of the situation like that.

  • Trying to avoid using any arithmetic operators, and sticking just to binary (extending beyond 16 bit unsigned ints is left as an exercise for the interested reader):

     
        
    #!/usr/bin/perl
    
    # This increments $i
    
    my $i=1;
    print "Start: $i ";
    
    if (($i & 0b1111111111111111) == 0b1111111111111111) {die "Overflow";}
    if (($i & 0b0000000000000001) == 0b0000000000000000) {$i=(($i & 0b1111111111111110) | 0b0000000000000001);}
    else
    {
            if (($i & 0b0111111111111111) == 0b0111111111111111) {$i=(($i & 0b0000000000000000) | 0b1000000000000000);}
            if (($i & 0b0011111111111111) == 0b0011111111111111) {$i=(($i & 0b1000000000000000) | 0b0100000000000000);}
            if (($i & 0b0001111111111111) == 0b0001111111111111) {$i=(($i & 0b1100000000000000) | 0b0010000000000000);}
            if (($i & 0b0000111111111111) == 0b0000111111111111) {$i=(($i & 0b1110000000000000) | 0b0001000000000000);}
            if (($i & 0b0000011111111111) == 0b0000011111111111) {$i=(($i & 0b1111000000000000) | 0b0000100000000000);}
            if (($i & 0b0000001111111111) == 0b0000001111111111) {$i=(($i & 0b1111100000000000) | 0b0000010000000000);}
            if (($i & 0b0000000111111111) == 0b0000000111111111) {$i=(($i & 0b1111110000000000) | 0b0000001000000000);}
            if (($i & 0b0000000011111111) == 0b0000000011111111) {$i=(($i & 0b1111111000000000) | 0b0000000100000000);}
            if (($i & 0b0000000001111111) == 0b0000000001111111) {$i=(($i & 0b1111111100000000) | 0b0000000010000000);}
            if (($i & 0b0000000000111111) == 0b0000000000111111) {$i=(($i & 0b1111111110000000) | 0b0000000001000000);}
            if (($i & 0b0000000000011111) == 0b0000000000011111) {$i=(($i & 0b1111111111000000) | 0b0000000000100000);}
            if (($i & 0b0000000000001111) == 0b0000000000001111) {$i=(($i & 0b1111111111100000) | 0b0000000000010000);}
            if (($i & 0b0000000000000111) == 0b0000000000000111) {$i=(($i & 0b1111111111110000) | 0b0000000000001000);}
            if (($i & 0b0000000000000011) == 0b0000000000000011) {$i=(($i & 0b1111111111111000) | 0b0000000000000100);}
            if (($i & 0b0000000000000001) == 0b0000000000000001) {$i=(($i & 0b1111111111111100) | 0b0000000000000010);}
    }
    print "End: $i\n";
    
      
  • Things I was not expecting to see first thing in the morning: number 1...

  • Ha! Faking key presses, truly an elegant weapon for a more civilized age. If it works, it works.

  • The thing that got me to switch was being able to maintain my pane layout between connections. The various window and pane management niceties (naming, swapping, listing and the like) got me to stay. Now you can keep your screen, but you'd have to pry tmux from my cold, dead, tty.