• 0 Posts
  • 42 Comments
Joined 1 year ago
cake
Cake day: November 23rd, 2023

help-circle







  • Ted Ts’o was way out of line in that conference and was clearly channeling his inner ca. 2001 Torvalds.

    I think Rust is a better path forward for a majority of the kernel/driver code maintained currently, but it is definitely going to take time for it to gain a foothold. I also think there is some condescension on both sides that is completely unjustified and needs to stop.

    The hardline C devs that don’t want to learn Rust need to accept that at some point they will have to either adapt or pass the torch, and that no amount of whining or bitching in public forums is going to change that.

    The Rust devs that are getting upset because people are “attacking” their favorite language need to accept that there will be substantial and impassioned resistance to making broad language changes to a set of projects that have existed for decades. It would be an uphill battle for any language to try to supersede C in the kernel; this is not a condemnation or attack on Rust or its zealots, it’s a matter of momentum and greybeard stubbornness.


  • In fairness, “I don’t want to maintain bindings for a language I never intend to use” is a perfectly reasonable position.

    The typical answer here is for the language evangelist to implement and maintain the bindings, and accept the responsibility of keeping them in sync with the upstream (or understand that they will be broken for however long it takes for another community member to update them).


  • This is not always true. Some tablets are extended release and if you break them apart the timing is thrown off. You get a higher dose initially, and the dose doesn’t last the intended period.

    A family friend learned this the hard way when they were breaking a seizure preventive tablet in half to make it easier to swallow; they’d often have a recurrent seizure about an hour or two before their next dose time.





  • felbane@lemmy.worldtoTechnology@lemmy.worldCrowdStrike Isn't the Real Problem
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    1
    ·
    4 months ago

    Rollout policies are the answer, and CrowdStrike should be made an example of if they were truly overriding policies set by the customer.

    It seems more likely to me that nobody was expecting “fingerprint update” to have the potential to completely brick a device, and so none of the affected IT departments were setting staged rollout policies in the first place. Or if they were, they weren’t adequately testing.

    Then - after the fact - it’s easy to claim that rollout policies were ignored when there’s no way to prove it.

    If there’s some evidence that CS was indeed bypassing policies to force their updates I’ll eat the egg on my face.


  • felbane@lemmy.worldtoTechnology@lemmy.worldUnofficial Reddit API
    link
    fedilink
    English
    arrow-up
    246
    arrow-down
    2
    ·
    4 months ago

    API access was only half the problem. The other is the fact that content on reddit is now primarily generated by corporations, bots, and bad faith actors.

    Going there for specific threads (e.g. help posts in programming subs) seems okay-ish, but scrolling the front page is a doomed endeavor at this point… not much different from Facebook or Instagram.