• 0 Posts
  • 104 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle

  • There’s no reason to be rude and insulting. It doesn’t make the other person look lazy; it just makes you look bad, especially when you end up being wrong because you didn’t do any research either. The article is garbage. It’s obviously written by someone who wants to talk about why they don’t like bcachefs, which would be fine, but they make it look like that’s why Linus wanted to remove bcachefs, which is a blatant lie.

    Despite this, it has become clear that BcacheFS is rather unstable, with frequent and extensive patches being submitted to the point where [Linus Torvalds] in August of last year pushed back against it, as well as expressing regret for merging BcacheFS into mainline Linux.

    But if we click on the article’s own source in the quote we see the message (emphasis mine):

    Yeah, no, enough is enough. The last pull was already big.

    This is too big, it touches non-bcachefs stuff, and it’s not even remotely some kind of regression.

    At some point “fix something” just turns into development, and this is that point.

    Nobody sane uses bcachefs and expects it to be stable, so every single user is an experimental site.

    The bcachefs patches have become these kinds of "lots of development during the release cycles rather than before it", to the point where I’m starting to regret merging bcachefs.

    If bcachefs can’t work sanely within the normal upstream kernel release schedule, maybe it shouldn’t be in the normal upstream kernel.

    This is getting beyond ridiculous.

    Stability has absolutely nothing to do with it. On the contrary, bcachefs is explicitly expected to be unstable. The entire thing is about the developer, Kent Overstreet, refusing to follow the linux development schedule and pushing features during a period where strictly bug fixes are allowed. This point is reiterated in the rest of the thread if anyone is having doubts about whether it is stated clearly enough in the above message alone.



  • I agree with you that the one liner isn’t a good example, but I do prefer the “left to right” syntax shown in the article. My brain just really likes getting the information in this order: “Iterate over Collection, and for each object do Operation(object)”.

    The cost of writing member functions for each class is a valid concern. I’m really interested in the concept of uniform function call syntax for this reason, though I haven’t played around with a language that has it to get a feeling of what its downsides might be.






  • The article kind of fumbles the wording and creates confusion. There are, however, some passages that indicate to me that the actual data was recovered. All of the following are taking about the NAND flash memory.

    The engineers quickly found that all the data was there despite Tesla’s previous claims.

    Now, the plaintiffs had access to everything.

    Moore was astonished by all the data found through cloning the Autopilot ECU:

    “For an engineer like me, the data out of those computers was a treasure‑trove of how this crash happened.”

    On top of all the data being so much more helpful, Moore found unallocated space and metadata for snapshot_collision_airbag‑deployment.tar’, including its SHA‑1 checksum and the exact server path.

    It seems that maybe the .tar file itself was not recovered, but all the data about the crash was still there.



  • patatahooligan@lemmy.worldtoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    107
    arrow-down
    7
    ·
    3 months ago

    I see a few top level comments agreeing with the sentiment that users are being entitled or abusive, but what are they actually referring to? The linked image certainly has no evidence of such behavior. Someone who claims to be the developer filed a deletion request for the duckstation-git AUR package on the AUR and they say:

    Every time, it turns into abuse towards me, as you can also see in the comments for the package.

    I read through a few pages of the comments here and they’re mostly people talking about fixing issues with the package, and what to do about the dev purposely breaking the build… I only found a single message that could be called abuse:

    @eugene, not really but i suspect it’s an uphill battle, check the commit message: https://github.com/stenzek/duckstation/commit/30df16cc767297c544e1311a3de4d10da30fe00c

    FWIW, I’m moving to pcsx-redux, I rather run a little bit less advanced PSX emulator than software by this upstream asshat. Regardless, much thanks for maintaining the AUR package so far.

    And even this is not a good example of what stenzek is describing. For one, it’s obviously a reaction to stenzek’s hostile changes and not the sort of user coming for support and being abusive that stenzek is talking about. The user is also explicitly moving to a different emulator and not expecting any change from duckstation.