[–] 2 points 3 weeks ago (1 child)

I dont know if I'd call them forks, they're more like unmerged branches.

Like the bulds with different schedulers, the only thing different about them is they include an extra module that's not included by upstream, everything else is a 1:1 match for upstream, and follows closely.

I'd personally say the real-time kernel would come close to it, but even that was still roughly tracking upstream, and was merged in the end.

  • source
  • parent
  • context
  • [–] 2 points 3 weeks ago

    I read through that whole discussion. None of it seems unreasonable. Considering Debian also wants apt to support replacing coreutils too, I don’t even know why you think it’s unreasonable. There is limiting behavior in apt, and both the Debian and the Ubuntu devs want it fixed. It’s a win-win.

  • source
  • parent
  • context
  • [–] 1 point 3 weeks ago (1 child)

    My bad, I was just trying to meet you halfway and not suggest that you don't actually know what you're talking about, because that would be rude.

    I don't really care what dpkg is written in but I do know two things for a fact: Ubuntu's coreutils upgrade broke Ubuntu because coreutils first gets removed, and Canonical's official response was "apt maintainers will have to clean up our mess": https://discourse.ubuntu.com/t/migration-to-rust-coreutils-in-25-10/59708
    My memory was wrong on one point: dpkg is the workaround, apt is what the linked post blames.

  • source
  • parent
  • context
  • [–] 2 points 3 weeks ago (1 child)

    They are equivalent. Your quote:

    This is exactly right and I love Linus so much for cutting through the emotion every time. All he cares about every single time is if the commit is good or bad. Thats how it should be.

    So the only thing that matters is that the commit is good. Not whether the commit turns on DRM for every Linux machine on the planet, not if the commit starts requiring age verification for every user, not if the commit fucking bombs every city on earth.

    Your reasoning is literally ignoring harm.

    I said nothing about profits or ignoring harm.

    No, you implied it with a dog whistle. And now you’re pretending like you didn’t.

  • source
  • parent
  • context
  • [–] 1 point 3 weeks ago (-1 children)

    Asking LLMs to find flaws, then verifying those flaws are real, is more powerful than just looking for flaws without the tool.

    No it isn’t. Your example is so contrived. What was happening before these documents were reviewed by LLMs? Were the lines that were incorrect causing issues? If so then a human would have found it years ago. If not then they weren’t causing problems and all the LLM has done is invent work that a human now needs to clean up. The LLM didn’t solve a problem, it created a new one!

    Now you need to pay a human to make sure that the LLM isn’t actually making things worse, which wasn’t even a job before! Your company that won’t pay a human to review the document in the first place is now needing more humans to clean up a mess that wasn’t a problem in the first place.

  • source
  • parent
  • context
  • [–] 1 point 3 weeks ago (-1 children)

    you’re acting like the solution here is LLMs

    No, you're imagining that's what I wrote. LLMs are a tool, not a solution.

    Fine, you’re acting like the tool for the solution is an LLM.

    A helpful tool, very helpful in some situations.

    X to doubt. My job is currently filled with people using LLMs and most of what I’m doing is undoing their shit our detangling whatever LLM output they paste

    The real problem that people and LLMs struggle with is: what should we be doing in the first place? LLMs don't solve that,

    Correct

    they do accelerate the making of a software thing when you know what you want that software thing to be.

    Incorrect. They accelerate making a ton of code that is impossible to maintain, update, etc. If you know what the software is, it was never writing it that was the hard part. That’s why senior+ developers have been saying for decades that the hard part of the job isn’t coding. It’s everything else.

    They also accelerating the finding of flaws during the process, enabling cleaning those flaws out faster.

    Incorrect. Like I said, half my job is reading over extremely verbose LLM bullshit from colleagues to tell them every single thing the LLM said incorrectly. That didn’t happen before LLMs. People checked their work. LLMs don’t have a mind, they cannot check their work.

    That's not a problem for tools to solve, that's a societal problem that goes back to - at least - the start of agriculture.

    I didn’t say it was a problem for tools to solve! But it sure is a problem tools can cause! And that’s exactly what’s happening here. It’s making everything so incredibly worse that there is literally no justification for it!

  • source
  • parent
  • context
  • [–] 1 point 3 weeks ago

    Nah the EU legislation made it so that it has to be watermarked (LLM output was not watermarked until that passed, it was just image and music output) and discernible with a tool to tell. So you can check if something is AI generated. Anthropic says it should work on code.

  • source
  • parent
  • context
  • [–] 2 points 3 weeks ago

    I think I'd use bazzite on a system that was exclusively an entertainment system, like a minipc hooked up to the tv. But that's super expensive to make myself ATM and I've already got a steam machine for that purpose.

  • source
  • parent
  • context
  • [–] 2 points 3 weeks ago (1 child)

    I don't like either, just go with a normal distro. All distros are nearly equal, shown in benchmarks over and over again. just pick your favorite package manager / release model, that's way more important than 2% more performance in archiving or some bs.

  • source
  • [–] 2 points 3 weeks ago

    Regarding the stopped working, after an update and before reboot I usually see videos, wine, and sometimes system settings stop working. But the only thing that breaks is ricochet-refresh client which is AUR and I think it is maybe not made how it should

  • source
  • parent
  • context
  • [–] 1 point 3 weeks ago* (last edited 3 weeks ago) (1 child)

    😉

    I have an anecdote where Noctalia Shell broke for me suddenly the other day for some unexplained reason. I imagine it had to do with upgrading the system, but Noctalia had moved from version 4 to 5 and development on version 4 is completely abandoned, so it didn't support my upgraded system or something.

    Anyway, so that was a matter of just installing a new Noctalia package. But that was maintenance due to what I had installed on my system, namely software from the AUR, and when I did that I signed up for it. 😅

  • source
  • parent
  • context
  • [–] 1 point 3 weeks ago

    I don’t recommend anyone use the AUR if it can be at all avoided.

    But I do; not everyone, but certain people. In example me as a certain people. I use the AUR since years and it has been great.

    The AUR is just a script that builds the package from source

    That's why its okay to use, if you know what you are doing and what you need.

    so you could just make your own bash scripts to do that?

    Exactly. But then it is not integrated into the other packages (when we speak about AUR helpers), which includes handling dependencies and other stuff. Also it is much better to use scripts from others that are well tested and checked and updated. With the caveat that you don't trust everyone and will always check the script and sources before updating.

    I don’t remember my cmake commands off the top of my head but I think it’s just

    It's not always just cmake. In fact there are many ways. Some even download pre-compiled binaries (from those sources you trust off course), others require custom work before making it work, with correct versioning and so on.

    Those bash scripts might also be in the repo as pkgbuild so you can copy it from there but you’ll have to change any ArchLinux specific command to debian.

    I do not recommend that, unless it is very clear this could work. Because the dependencies are different. But with care and knowledge, as a starting point one could probably simply change scripts to make them work on Debian.

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