• 0 Posts
  • 50 Comments
Joined 1 year ago
cake
Cake day: November 13th, 2023

help-circle


  • Fuck that.

    I strongly dislike how the argument hinges on the very movable goalpost of “illegal” drugs. It has this awful moralizing “protect the kids while we destroy privacy”, vibe to it.

    At first I though this would require an end-run on HIPAA, but all they really need to do is re-schedule a bunch of therapeutic drugs. Or ignore the FDA entirely and just enforce a ban by edict (somehow) through a different agency. I don’t think we’ve ever seen federal agencies openly disagree like that before, but I think it’s possible. Also: big pharma may have something to say about all this.

    Like a lot of the nonsense coming from this cabinet, it’ll test the crap out of state’s rights.


  • Fine, then it’s not a political party outright, and instead a lobby. Or a trade association. Or a big bunch of very angry like-minded voters. The point is that such a group could exert leverage within the DNC coalition as a voting block. We already have these for other interest groups. DNC membership is really only useful for voting in primaries to most people anyway - it doesn’t have to signify allegiance or kow-towing to party power.









  • I’m starting to wonder if all that are symptoms of a company using information technology to it’s most powerful extent.

    Services like Door Dash couldn’t exist at the current scale, speed, and service without the internet and highly capable phones/laptops/whatever in everyone’s home. It enabled this kind of gig economy service to come out of nowhere, build very rapidly, and disrupt the market before the law or even social norms could ever hope to step in. But as a consequence of all that, the owners cannot help themselves, and continue with their “Greed% speed run” of running a company straight to its conclusion. Every mistake, every error, every bad take, it’s all accelerated right alongside the good stuff. It’s like enshittification on amphetamines.


  • dejected_warp_core@lemmy.worldtoLinux@lemmy.mlThoughts on this?
    link
    fedilink
    arrow-up
    71
    arrow-down
    8
    ·
    edit-2
    11 months ago

    TL;DR: the author needs to do a better job of citing sources and building an argument.

    The author’s argument from self-appointed authority tone aside, I dug into the only two verifiable pieces of evidence cited. These are almost impenetrable to the outsider, and even with plenty of coding experience behind me, I’m having to go deep to make sense of any of it. After all, sometimes, bugs and design decisions are the result of a best effort in the situation at hand and not necessarily evidence of negligence, incompetence, or bad architecture. There’s also something to be said for organizing labor, focusing effort on what matters, and triaging the backlog.

    The original author really needs to pony up a deeper digest of the project, with many more verifiable links to back up the various quality claims. If anyone is going to take this seriously, a proper postmortem is a better way to go. Cite the version reviewed, link to every flaw you can find, suggest ways to improve things, and keep it blameless. Instead, this reads like cherry picking two whole things on the public bug tracker and then making unsubstantiated claims that’s a part of a bigger pattern.

    My personal take on what was cited:

    1. I’m grossly unqualified to assess this codebase as a Wayland or GUI programmer, but work plenty in the Linux space as a cloud practitioner and shell coder.
    2. The first article smells like inadequate QA for cases like placing Wayland programs in the background, which is not typically done for GUI apps under normal usage (IMO).
    3. The second article is a two-line change that I suppose highlights how ill-suited C is for this kind of software. Developer chatter on the MR suggests that the internal API could use some safeguards and sanity checks.
    4. 162 open issues, 259 closed, oldest still open is five years old. Not great, but not terrible.
    5. None of this is particularly egregious, considering the age of the project and the use it enjoys today.

    Links:



  • Hard disagree there. Driving on the interstate south of San Antonio, there are these overpasses that are, inexplicably, on the highway itself. These are artificial hills that are steep enough at highway speeds, that your visibility is made shorter than your stopping distance. You can’t see past the top until you’re there, and they completely obscure the entire highway on the other side because it’s so straight. Obstructions, stopped vehicles, pile ups, anything could be on the other side and you wouldn’t know. Anyone on cruise control or driving a semi has their trip peppered with these possibly lethal moments at regular intervals.

    Everywhere else I’ve been in the lower 48, (slower) local roads pass over freeways, because it literally takes less dirt to make that safe.