Comment on My poor RAM...

• habanhero@lemmy.ca ⁨1⁩ ⁨year⁩ ago

  It has all this support for native platforms yet it’s always a clunky memory hog

  Maybe so but it has improved a lot over time. The app devs share some responsibility too so it’s not all on Electron.

  zero effort to respect the design language of the OS it’s running on.

  That’s the Dev’s design choice, not a limitation of Electron.

  I’m on macOS, I want the app to be a native macOS app. If I wanted it to look like a webpage, or Windows, or Linux GTK then I’d switch to one of those and expect it to match those paradigms.

  I don’t disagree but at the end of the day it doesn’t matter to enough people for it to become an issue. People are used to Slack and the way it works.

  Moreover the cost of building the same app 2x or 3x simply doesn’t make business sense.

  source

  • railsdev@programming.dev ⁨1⁩ ⁨year⁩ ago

    I’m a web developer but is there no concept of classes, libraries, etc in other programming languages?

    What happened to writing the “core” of an app that doesn’t rely on UI then simply writing the front ends for each platform you want to support?

    You keep saying Electron is used for better compatibility and listing out Linux, Windows, macOS but here’s the thing — most companies are only targeting those. That’s just three (if you don’t write for a million desktops on Linux).

    Is it really so hard to support just three environments with only the UI being tailored for the OS it’s running on?

    Honestly, it just feels like poor tooling and a poor excuse.

    source

    • habanhero@lemmy.ca ⁨1⁩ ⁨year⁩ ago

      What happened to writing the “core” of an app that doesn’t rely on UI then simply writing the front ends for each platform you want to support?

      What do you mean? I can’t speak for Slack but I’m sure some degree of business logic / client side logic separation exists.

      By the way, what you just described is the essence of cross-platform development, rather than an argument for building apps natively.

      simply writing the front ends for each platform you want to support?

      But why would you rewrite the “front-end” for each platform if you have one you could just port over? Who is going to pay for those 2x developers and what would be the ROI on this effort?

      That’s just three (if you don’t write for a million desktops on Linux).

      Is it really so hard to support just three environments with only the UI being tailored for the OS it’s running on?

      In Slack’s case I’d wager the answer to be a resounding YES. I don’t think you fully grasp the full scope Slack’s capabilities, and the amount of work involved to build native clients for not just one or two, but three different platforms - it’s definitely not just the “UI”.

      Honestly, it just feels like poor tooling and a poor excuse.

      Quite the opposite - frameworks like Electron let’s devs with your skillset build with the stack you already know, and abstracts away quite a bit of the cross-platform complexities, which strangely enough is what you are suggesting but also what you are arguing against

      source