• @footfaults@lemmygrad.ml
    link
    fedilink
    English
    1313 days ago

    This is the same thing that happens with desktop applications that use Electron. They have performance issues and eat tons of RAM.

    Apparently it’s too difficult to pay good programmers that can use native frameworks and lower level programming languages, it’s just cheaper to hire junior developers who only know JavaScript and just make everyone deal with the performance degredation

    • GaveUp [she/her]
      link
      fedilink
      English
      813 days ago

      Microsoft is too busy laying people off every year arbitrarily for the almighty stock price and offshoring to cheap labor sorry

    • DefinitelyNotAPhone [he/him]
      link
      fedilink
      English
      713 days ago

      The core idea of Electron makes a lot of sense: rather than try to make your program run on many different OSes you instead just make it work on one platform that then makes it run on many different OSes for you. It’s effectively a bunch of development teams centralizing their OS-driven development to a third party.

      The problem is that Electron is made by capitalists who only care that it works on Windows/MacOS/iOS/Android/etc and couldn’t give two shits if the performance is good or not because that’s not what they get paid to do, so it’s massively resource intensive and slow as balls.

      • @footfaults@lemmygrad.ml
        link
        fedilink
        English
        2
        edit-2
        12 days ago

        This was the premise of Java, specifically AWT and Swing. Electron is following a path that was already explored decades ago and the same performance and memory problems were encountered