• AlotOfReading@lemmy.world
    link
    fedilink
    arrow-up
    10
    ·
    edit-2
    4 months ago

    You can sometimes deal with performance issues by caching, if you want to trade one hard problem for another (cache invalidation). There’s plenty of cases where that’s not a solution though. I recently had a 1ns time budget on a change. That kind of optimization is fun/impossible to do in Python and straightforward to accomplish Rust or C/C++ once you’ve set up your measurements.

    • Possibly linux@lemmy.zip
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      edit-2
      4 months ago

      Don’t throw the baby out with the bath water. There are many applications that don’t have performance needs such as a calculator app

      • AlotOfReading@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        4 months ago

        You can find plenty of people complaining online about the startup time of the windows and gnome (snap) calculators. The problem in those cases isn’t solved by compiled languages, but it illustrates that it’s important to consider performance even for things like calculator apps.

    • MeanEYE@lemmy.world
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      4 months ago

      Which is exactly what I said. Most of the times you can work around it. Sure cache invalidation can be hard, but doesn’t have to be. If you need performance use more performant language. Right tool for the job.