“Falsehood flies, and truth comes limping after it, so that when men come to be undeceived, it is too late; the jest is over, and the tale hath had its effect: […] like a physician, who hath found out an infallible medicine, after the patient is dead.” —Jonathan Swift

  • 128 Posts
  • 342 Comments
Joined 1 year ago
cake
Cake day: July 25th, 2024

help-circle
  • Here’s what a 7.62x63 (“.30-06”) does to level III armor (think basic rifle protection, the kind that would actually stop the round that hit Kirk). This particular one is a large, very conspicuous plate of steel 8.5 mm thick and weighing 4 kg. You don’t just slot this in under your shirt and look totally normal. If Kirk had done the lowest-profile possible thing and duct-taped the plate around his torso, you would still notice it under his clothing.

    And it would have to have been hard armor, i.e. a rigid plate. Soft armor 1) wouldn’t have stopped that round (that’d be more like a step down to level IIIA on the high end) and 2) would’ve embedded the round rather than ricocheting it.


  • Firstly, the burden of proof says it’s their job to demonstrate that Kirk was wearing a bulletproof vest in the first place (let alone that the bullet struck him in it first), not yours to debunk it. We’ve really lost sight of how important this is in recent years.

    • There’s zero evidence Kirk was wearing body armor whatsoever.
    • I don’t think we’ve ever seen evidence of Kirk wearing body armor to debates elsewhere.
    • A bullet would’ve left at minimum a noticeable tear in Kirk’s clothing.
    • Neither journalists nor investigators mention anything about this even though there’s zero compelling reason for them not to and, for journalists, incentives to do so.
    • The round was 7.62x63 mm fired from a bolt-action rifle.
    • If that round strikes body armor, in order for it to stop (let alone ricochet rather than embed), the armor needs to be so thick that you cannot hide it under civilian clothing like Kirk’s. The armor would’ve been readily visible to everybody in attendance. Light armor Kirk realistically could’ve been wearing would be a non-factor.
    • Even if this magically happened, the improbably fucked-up physics required for a bullet to bounce from the torso into the cartoid artery seem vanishingly unlikely at best and implausible at worst.

    While much of this just shows extreme unlikelihood, the thickness of the alleged body armor is impossible to reconcile with the round and the weapon it was fired from.










  • TheTechnician27@lemmy.worldtoLemmy Shitpost@lemmy.worldpunishment
    link
    fedilink
    English
    arrow-up
    102
    arrow-down
    1
    ·
    edit-2
    1 month ago

    It’s both because:

    1. Successful murder does more actual harm, and thus if you weigh not just intent but actual harm, you get a more severe punishment (think, for example, of felony murder, where the perpetrators don’t necessarily intend to kill anyone but someone does die as a result of them committing a felony).
    2. Treating murder more harshly than attempted murder gives someone attempting murder a practical incentive not to follow through and finish the job.









  • TheTechnician27@lemmy.worldtoProgrammer Humor@programming.devHello, Linux Developer
    link
    fedilink
    English
    arrow-up
    30
    arrow-down
    2
    ·
    edit-2
    2 months ago

    Not sure how this applies when:

    • X11 was the only standard prior to Wayland.
    • GNOME is dropping X11 in a short time.
    • KDE’s telemetry even five months ago showed 80+% of (that portion of) their userbase uses Wayland, and they plan to drop X11 once they have a concrete set of problems worked out.
    • Hyprland and Sway run Wayland exclusively.
    • Cinnamon, MATE, and Xfce are working on Wayland sessions. Cinnamon’s is there but, I think, still experimental.
    • Budgie is working to go Wayland-only.
    • There’s no sign that Wayland will stop improving from a state that’s arguably already much better than X11.
    • X11’s actual maintainers barely want anything to do with it beyond bug fixes, and the only person who wants to “innovate” it via a fork is a bigot and a fucking moron who doesn’t know things you learn in CS 101.
    • X11’s maintainers are majorly involved in developing Wayland and have been since the start. This is their idea.

    It seems like it went from “Situation: there is one standard” to “Situation: there are two standards developed by largely the same people with one set to replace the other”, and then soon: “Situation: there is one standard and one translation layer kept around for a decade or so for compatibility.”

    Not every single time someone tries to make things better is this xkcd relevant; this had nothing to do with unifying standards and everything to do with superseding one.


  • TheTechnician27@lemmy.worldtoProgrammer Humor@programming.devHello, Linux Developer
    link
    fedilink
    English
    arrow-up
    24
    arrow-down
    1
    ·
    edit-2
    2 months ago

    Has anyone so far stopped you from using your outmoded tangle of garbage? Or do you just not like that major desktop environments are switching to more sensible defaults?

    If you’re worried about GNOME 50 dropping X11 in the future… okay? Nobody’s obliged to maintain your shit. Linux is all about choice, and it’s their choice not to spend untold thousands of hours working to keep X11 usable, just like it’s your choice to change your Linux to something that does still use it. Switch to any one of the other desktop environments; see if the Wayland Illuminati or whatever gives a shit.