[–] 2 points 1 week ago

It's not that simple from the manufacturers perspective.

Setting up a new fab takes years. Usually 5 or more for a grounds up build. Less for an upgrade (1-2 years or so). Lots of in-progress fabs have been sped up and we will see more supply sooner, but not soon enough.

Making less HBM and more DDR RAM doesn't make sense for $hareholders, so we are stuck with getting supply at a trickle such that the marginal cost for both is equal or it's a contract with a penalty larger than any profits

  • source
  • parent
  • context
  • [–] 5 points 1 week ago

    Simply lovely. There long names are for mounting since they are persistent w ross reboots.

    The short ones can change of there are no mounting options or more or fewer devices than before.

    PS: even the networking devices have this funky naming

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

    Once a model knows python 3.14 there's little need to update it until 3.14 is EOL. Most professional settings pin dependencies and runtimes and only move them for security issues or planned migrations.

    Several embedded platform only support C++14 as the latest target. That's a lag of 10 or more years. This is similar to how the calculator chips are redone once a decade or so depending on new fab process giving enough benefits. Once something gets used for years, a large investment makes more sense than the current senseless frontier models every month or two.

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