[–] 2 points 1 year ago (2 children)

No argument.

I do not see much chance of a middle-man though and the alternative means much less adoption.

My issue is not with Kent’s strong technical opinions. I like those. Well, except that abusing other people as cover for his inability to follow the rules is not cool.

Linus can be a dick but he is typically making technical arguments at least (and usually quite good ones). Kent likes to play the “engineering” card but the drama is always about process, not technology, and he is the one being called out. So trying to pretend he is defending better engineering just makes the behaviour worse.

NVIDIA were breaking the rules (legally even). They have come around.

More big endiian in the kernel for no reason is a negative.

Not sure about the Intel engineer. Linus can be a jerk though so not assuming he was right if I do not know the situation.

  • source
  • parent
  • context
  • [–] 19 points 1 year ago

    And, while I like old hardware, the first x86-64 chips shipped in 2003. So, this is not exactly a Windows 11 situation.

    Hardware older than that is going to struggle with modern browsers. A PC from that era would probably have less than 1 GB of RAM and perhaps a max RAM well under 4 GB (the theoretical limit). Using older software versions is probably best anyway.

  • source
  • [–] 15 points 1 year ago (4 children)

    The replies here make me so mad at Kent Overstreet.

    I love bcachefs and was using it on quite a few systems. When it was in the mainline kernel, interest was building. I feel like we could have been just a few months from experimental coming off and adoption skyrocketing.

    Then Kent got it pulled from the kernel (so not interested in the “fighting for users” misdirection). Now, as evidenced by the comments here, most users will not touch it.

    I needed it in the kernel so I have been migrating away too but it breaks my heart.

    I am sure somebody will use it, maybe even more than the small number that have historically. And Kent will probably tell himself that is ok.

    It sucks.

    Now, I did not write a COW filesystem. So I guess I am getting what I am owed (nothing). That does not dull the sting much though.

  • source
  • [–] 3 points 1 year ago

    Niri is absolutely the best tier for a laptop with a smaller screen. It provides all the benefits of tiling without the tiny, cramped windows that tiling tends to result in.

    On other tilers, you end up using workspaces for single apps to avoid splitting the screen.

  • source
  • [–] 6 points 1 year ago

    The official statement from the CPC pretty much confirms the culture he is talking about. This statement absolutely drips petty, vindictive, childishness.

    "Chris d'Entremont, who established himself a liar after wilfully deceiving his voters, friends and colleagues because he was upset he didn't get his coveted deputy speaker role, is now spinning more lies after crossing the floor. He will fit in perfectly in the Liberal caucus," a spokesperson for the Office of the Leader of the Official Opposition (OLO) said in a Sunday morning statement to CBC News.

  • source
  • [–] 6 points 1 year ago* (5 children)

    The industry cannot code safely. There are many reports, studies, and corporate disclosures highlighting that memory related bugs are the primary source of critical security issues in C and C++ code. That is why even NIH companies like Google and Microsoft are adopting Rust in their core products.

    That you want to publicly ignore all that evidence to paint it as an individual skill issue does not come across as competent or intelligent. Few of us are going to assume your code is free of these kinds of bugs.

    The fact that your have to say it so dismissively makes me think that you know it too.

  • source
  • parent
  • context
  • [–] 4 points 1 year ago

    The timeline is not super abrupt, especially for architectures where all he is asking is to ensure that your Rust toolchain is in order. That is especially true when you consider that Rust is already well maintained on all the Debian architectures that people actually use.

    The abruptness (almost rudeness) is in the second part where he basically says that, if you cannot get Rust going in time, you should just stop releasing Debian for that architecture.

    It is mostly just poorly worded though. Because none of these architectures have “official” support even now. This will not be the only way they are behind. So, there is not reason to be so dramatic.

    And that would be my response to him. Another option here is that these alternative architectures just continue to ship an older version of APT for now. Emergency avoided. Few of them ship with up-to-date versions of APT even now.

    Another solution is to use one of the multiple projects that is working to make Rust code build with the GCC compiler back-end. At least one of these projects has already announced that they want to work with these Debian variants to ensure that APT builds with them.

    So, the 6 month timeline is a reasonable impetus to make that happen which would be quite a good thing beyond just APT.

    There are many other useful tools written in Rust you are going to want to use on these architectures. It will be a fantastic outcome if this pressure from APT kickstarts that happening for some of these long abandoned architectures (by the mainstream at least).

  • source
  • parent
  • context
  • view more: ‹ prev next ›