[–] 4 points 1 year ago* (last edited 1 year ago) (1 child)

think it's fair to say performance rust is hard to write

This situation proved exactly the opposite.

They wrote a utility to pass functional tests. It did. Then people said it was too slow. So, in just a few days or hours, they dramatically sped it up while still passing the tests.

Seems like it was pretty easy to write fast Rust code in this case.

  • source
  • parent
  • context
  • [–] 8 points 1 year ago* (1 child)

    The best thing about all the C smugness here is how quickly it backfired.

    Out of dozens of utilities in uutils, two were slower than the GNU equivalents. In case the logic escapes some, that means that the others were already as fast or faster. Some are multiples faster. The overall uutils suite is faster then GNU Coreutils already and will only get better. There was nothing for C fans to be smug about to begin with.

    Of the two that were slower, it seems to have only taken a few days to make them faster. The article only tells us about one which is now 50% faster than the GNU version.

    But the promise of Rust is not that Rust is faster anyway. It is that it is easier and safer to refactor. The actual promise of Rust is that you can address issues like performance without as much fear that you will break everything.

    After the reported slowness, both of the two uutils implementations were dramatically sped up in just a couple of days or even hours. They are tested against the GNU test suite and so we know these tests are still passing. That is the promise of Rust. This example proves the Rust claims real. The C smugness did not age well.

    The C versions (GNU) can clearly be sped up as well. The question is who will do that and when. Because speeding up old C code is not nearly as easy or fun. My guess is that it is going to be more than a couple days before we see headlines bragging that GNU has caught up.

    The GNU Coreutils are maintained by Red Hat if we look at who contributes the code and who maintains the dev servers. They are professionally maintained. It is not a rag tag bunch of amateurs. So if uutils is already faster, it does not bode well for the C implementation.

  • source
  • parent
  • context
  • [–] 1 point 1 year ago

    Debian Stable is only supported for 3 years really and then 2 more years by the LTS team. The kernel and perhaps a few core libraries can supported up to 10 years by The Linux Foundation.

    You really need to migrate to newer versions every 3 - 5 years. Perhaps by “reinstall” you mean having to wipe and start over.

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

    Well, I certainly do not want the government making it harder for the economy to succeed at this exact moment. That is for sure.

    I am not sure people understand the danger we are in. If we have a second Great Depression, the climate is going to get screwed. I promise you that.

    As for EV charging standardization. The market has already done this. Tesla style chargers are now the NACS (North American Charging Standard) and pretty much all new EVs are being manufactured to that standard.

    If we stopped taxing foreign EVs, ICE emissions would also take care of themselves. Predating the mass adoption of EVs seems like quite a big gift to the fossil fuel industry.

    That said, no pipelines in Carney’s nation building projects. That seems like a pretty big miss if the goal was “support for the fossil fuel industry from top to bottom”.

  • source
  • parent
  • context
  • [–] -1 points 1 year ago* (last edited 1 year ago)

    In terms of timeline, you are right. However, I think that change was pretty obviously a continuation of Red Hat’s strategy. No IBM meddling required in my view.

    You could also state the situation quite differently.

    First, you could point out that Red Hat announced a developer license that offered up to 16 installations of RHEL for free. Press releases at the time quoted Red Hat execs saying they were not interested in going after users of “just a few servers”. Many of the users of CentOS at the time could have migrated to the real thing for free. These programs have only expanded. You can use Podman, Docker, or Distrobox to create an unlimited number of official RHEL instances without any commercial restriction.

    Second, Red Hat founded the CenttOS Stream project, moving their active development much more into the open. They shifted significant investment into this project. All the explanations at the time were about streamlining the development and engineering process.

    Third, Red Hat has increased the amount of GPL code they have contributed since then and started several new wildly popular projects all licensed under the GPL.

    Forth, they continued to explicitly and openly publish (for many years) all the input assets that CentOS was built from. This is how so many CentOS replacements were able to so quickly appear (Rocky, Scientific-now Alma, etc). IBM stopped directly paying for CentOS but did very little to kill it beyond that.

    If you were paying attention to any of the above, you may have missed a dramatic shift in behaviour and values resulting from the IBM acquisition.

    It does seem that IBM may be asserting themselves more now. That said, it is worth noting that they are only assimilating support services (legal, finance, Ops, IT, HR). The engineering and product teams (and their leadership) remain independent. Optimistically, this will not impact the Red Hat technology or community strategy. This is all pretty standard “economy of scale” stuff aimed at saving a bit of money on duplicated infrastructure. No immediate cause for alarm that it indicates a shift in strategy or even a desire for greater control by IBM corporate.

    All that said, it is hard to imagine that departments like legal and HR reporting directly into IBM will not result cultural influence at Red Hat that will inevitably bleed into the product side. It will certainly change the experience of being a Red Hat employee.

    I worry more about the unintended consequences. I am not a Red Hat customer. I do not use RHEL or Fedora. However, I recognize that Red Hat is the primary author of a lot of the software that I use. I do not even use GCC, Glibc, GNOME, or Systemd (all completely controlled by Red Hat) but I still rely on A LOT of their stuff.

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