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/)UN
unknownuserunknownlocation @ unknownuserunknownlocation @kbin.earth
Posts
1
Comments
26
Joined
3 wk. ago

  • I'm not saying it shouldn't be safer. I would much rather see Amtrak there, in large part because of their safety record. What I'm saying is that Bright line is still safer than cars. So yes, ensure Bright line increases its safety standards, but it's not a reason to argue against expansion of the Brightline network (unless, for instance, you want to argue for Amtrak expansion instead - then I would be on board), as it still is shifting people from a more dangerous to a safer mode of transit, even if there is plenty of room for improvement in that safer mode of transit.

  • The point of these next gen file systems aren't raw performance, they are reliability, performance for specific cases, and reduced data usage. For example:

    • Copy on Write means it's very performant to create snapshots
    • incremental backups are much quicker
    • checksumming means the filesystem directly and reliably detects data corruption
    • built-in support for raid means a simplified setup and integration of scrubbing features into the filesystem, which can then take advantage of checksumming etc.
    • deduplication can automatically recognize duplicated data and as such reduce data use

    These are things that tend to reduce performance, not increase it. Which is why, when performance on these filesystems stays the same or even increases, that's a major accomplishment.

  • Ob Döner oder Drehspieß hat nur mit dem Fleischanteil zu tun. Hähnchendöner darf es nach wie vor geben. Also zumindest theoretisch machen sie da nichts falsch solange der Fleischanteil hoch genug ist.

  • Yup, I saw that one as well after I left this comment. It showed really well not only that this is the largest number of journalists killed in such a conflict, but by really, really far. And did it in a way that shocked even me.

  • You don't have to apologize for "therapy speak" - this is off my chest, after all. And it seems, it needed to get out, you needed to tell someone, you wanted to be heard. And that is completely legitimate. In fact, it's a step in the right direction - you've come from bottling it up to telling someone - even if it's "just" on the internet. It's a important step forward.

    What you're feeling is entirely justified. What happened to you is unacceptable, and high blood pressure or whatever else is no excuse. Most importantly, it's not your fault. You had a right to a proper childhood.

    I don't know how the healthcare situation is where you live, but I would recommend looking into therapy. It's not an overnight cure, give it plenty of time - I mean, years. It will be worth it.

    Also, I don't know if you still live with your mother - if you do, I would be sure to move out. Find an apprenticeship you like, find an interesting job, an interesting field of study, something that gets you amount like minded people. Maybe there are some programming related jobs around? If you already have a history on whichever git platform, that can look great on a resume.

    Sending you a hug from the other side of the internet. It's going to be OK.

    P.S. Many adults don't really feel much like adults, either. You're in good company.

  • I watched that segment. I remember them saying very clearly that Israel didn't allow them to film it. So you know what they did? They showed footage from the ground, and didn't mince words as to how horrific things were. They showed the landscape, where barely anything is standing. They showed people digging through the ground looking for spilled kernels. There was absolutely no way you could watch that report and not understand the insanity of what is going on there.

    In fact, anyone who follows CBC's news coverage has no reason to not understand the depths of the horrors happening in Gaza, or in Palestine in general. They don't shove it into the corner. They place it center stage. Again, and again, and again. As if to say, "don't forget what is happening here".

    The CBC definitely has its faults, but this article is blowing things way, way out of proportion.

  • I might not have everything, but here's the best summary I can put together:

    This back and forth has been going on for a while now. The main complaints more recently have been the timing of his pull requests, and just generally his attitude and cooperation with others. The most recent spat was because he submitted a feature in the rc3 merge window, whereas you're only supposed to submit Bugfixes in that time frame. The feature in question was a journal rewind function, which would essentially move the filesystem back in time, which could fix an issue that did crop up in the testing phase. As such, he saw it as a workaround to fix an issue that had arisen, and so despite it technically being a feature, he saw it in the category of Bugfixes. The caused major disagreements as well as the way he talked with others. And now his pull request for rc1 has been simply ignored by Linus.

    The point where Kent is coming from is that he wants a rock solid file system, and he's following a bit of a take no prisoners approach to reach that goal. He seems to get most of his income from his following on Patreon, and so his focus is squarely on the users. With that focus, he seems to lose sight of other things, especially the cooperation with others in the kernel team. In fact, a number of people he has sparred with have shown decent respect for his code recently, saying the problem is really the cooperative aspect. One of the main reasons for bcachefs is also the lack of a proper CoW-filesystem in the Linux kernel that doesn't have the kinds of problems that btrfs has. And the fact that he states this and also talks about the lessons he's learnt from btrfs's shortcomings rubs a number of people the wrong way.

    Now here's some stuff I read into this personally: I have the impression that Kent looks up to Linus in a way. And they're actually both kind of similar: they both are extremely talented engineers, they both saw something missing in the software landscape and said "fuck it, I'll make it myself", and they both can be pretty serious dicks. I mean Linus managed to get suspended from his own damn project for being a dick - now that's an achievement. He's older now and somewhat calmer, but even recently he had quite the outburst on the mailing list. And I get the impression I get is that Kent (probably subconsciously?) has an attitude of "if he can do it, so can I". Which would be fair (even though it is poisonous), the only problem being Linus having the longer lever.

    Then there's the aspect of his mental health. He has said multiple times that his mental health has been suffering, which honestly doesn't surprise me. And if you look at his responses in different places, there seems to be quite an up and down. In some cases, he's very respectful to Linus, and in some cases he's pretty nasty (yes, Linus level nasty, but still). As far as I can tell, he needs a break and therapy. The only problem being, bcachefs has quite the momentum currently, and it wouldn't exactly be great for the project to lose that momentum, either. (Mind you, probably still better than being kicked from the kernel)

  • Unpopular Opinion @lemmy.world

    Nice guys often do finish last, and I'm tired of hearing the opposite