• jacksilver@lemmy.world
    link
    fedilink
    arrow-up
    12
    ·
    3 days ago

    My biggest issue with it is that it runs everything in the cloud. So you’re shipping your data to Microsoft and have latency to run anything. Seems insecure and added complexity to get a bit more out of excel.

    • morbidcactus@lemmy.ca
      link
      fedilink
      arrow-up
      9
      ·
      3 days ago

      Oh seriously? When there were rumblings of it coming years ago, I just assumed it would be implemented as a VBA successor, have everything local but just baked into excel. I guess I shouldn’t be that surprised though…

      • jacksilver@lemmy.world
        link
        fedilink
        arrow-up
        5
        ·
        3 days ago

        Yeah I was really disappointed when I heard it was a cloud solution. I think it’s due to complexity of python runtime environments, but I doubt msoft minds the opportunity to take more control.

    • rhymepurple@lemmy.ml
      link
      fedilink
      English
      arrow-up
      9
      ·
      3 days ago

      I agree with everything you said, but (in Microsoft’s eyes) this is a feature - not a bug.

      Without this cloud component, how could:

      • Microsoft make sure that the accounting team does not introduce a malicious/old Python library into the Excel file?
      • Microsoft protect its users from writing/running inefficient, buggy, or malicious Python code?
      • Microsoft provide a Python runtime to users who do not know how to install Python?
      • Microsoft charge to run code that you wrote in a free, open source software programming language on a device that you own?