[–] 2 points 10 months ago (1 child)

It has really only been a problem since GTK4. A lot of the rest of the GTK universe has stuck with GTK3. Now we are seeing people come up with alternative versions of libadwaita.

We should end up seeing a fork on the GTK side with GNOME going one way and everybody else another.

  • source
  • parent
  • context
  • [–] 6 points 10 months ago (4 children)

    I always preferred GTK and its ecosystem. But GTK is more and more positioning itself as just a toolkit for GNOME. And GNOME is more and more going not only going its own way but also not concerning itself with compatibility beyond what I will call the Red Hat Linux platform.

    So I can certainly see why anybody outside of GNOME would consider migrating off GTK. I mean, this is basically how we got COSMIC as well, based off the Iced toolkit.

  • source
  • parent
  • context
  • [–] 2 points 10 months ago

    It may be that they are picking geographically close mirrors that are massively slower. The difference between connecting to a very remote mirror can be up to a couple hundred milliseconds latency and a few percent in bandwidth due to “the Internet” itself.

    But the mirrors themselves can vary massively in performance. First, it may be older hardware that gets more easily overwhelmed. But it may also be on a connection with far less bandwidth. If that outgoing bandwidth is being shared across many users, you may not be getting much of it.

  • source
  • parent
  • context
  • [–] 1 point 10 months ago

    I am fortunate enough that the speed of the package manager itself would make a bigger difference.

    But connecting to a slow mirror can be a killer so, If that was a frequent problem for me, it would absolutely factor into my decision.

    I guess the other factor is how often you are updating. For a rolling distro, it would be essential.

    On Debian Stable, I would care a lot less. Just let it update overnight once in a while.

  • source
  • [–] 1 point 10 months ago* (last edited 10 months ago)

    As somebody with a dozen workstations running MUSL, I disagree. But you are going to want to use a performant allocator.

    The issue with C libraries is that you will have problems using pre-compiled binaries that are dynamically linked against a different C library.

    If I gave you a binary dynamically linked against MUSL, it would not work with Glibc either. It is not some kind of MUSL deficiency.

    The issue of course is that most pre-built proprietary software was built against Glibc. The proprietary NVIDIA drivers are a good example. But all the in-tree GPU drivers are fine.

    There is gcompat which pretends to be Glibc and forwards calls to MUSL from software that is trying to call Glibc. That may be enough to make things work sometimes.

    So there are two answers to “what works with MUSL?”.

    The first answer is that, if the software is linked with MUSL when it is built, almost everything works. A musl based distro could have a huge package library.

    The second answer is that, if you are trying to run software that was dynamically linked against a different C library when it was compiled, then basically nothing works. This is no different than missing any other dependency. Gcompat is a hack that makes programs use MUSL when they try to call Glibc, and that will work some of the time.

    As an aside, MUSL allows you to statically compile programs which means they include the C library in their binary. This allows these programs to run regardless of what C library is available on the local system. For this reason, MUSL is often used to create static binaries even on systems that use Glibc. Pacman on Arch is a good example.

  • source
  • parent
  • context
  • [–] 2 points 10 months ago (2 children)

    I don’t use Google Crashpad but when did you last try it.

    I just read a bug report that says it fixed building on MUSL in 2023. The fix was to comment out a reference to user_vfp in thread_info.h and to put the change in an #ifdef.

    I assume this is in the mainline by now.

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