Genuine question, why does it matter? Why shouldn’t a project choose a production ready method of creating cross platform compatible code to avoid duplication of efforts and cost?
Because when I’m looking for where all my RAM went and realise I’m running 7 instances of Chrome browser for no reason. Meanwhile an actual instance of Chrome with ~20 tabs is still a single instance, but with multiple threads.
because most people use more than one program at the same time? fire up that one along with, I dunno, Spotify and Discord and Slack, and suddenly your midrange laptop’s RAM is all but gone.
Because many users often enjoy using a dedicated application than a website. Plus it gives developers access to even more customization than browsers normally provide.
If they customers didn’t like using it, companies wouldn’t keep making these apps.
Personally, I’m a techie guy but I get exhausted with the number of tabs i have open at any time. I don’t need to have more dedicated to just slack, Spotify, discord etc
Oh the fact it’s cross platform is not the issue, the issue is that Electron sucks. There are better alternatives available like Tauri, yet companies keep using Electron because that’s what their developers know and they’re afraid to try something new.
If I’m a company and want to bring something to production quickly, what should i choose:
A relatively new tool that has seen barely any production use and thus could have a bunch of unanticipated problems. Also nobody uses it so every new engineer you bring onto the project has to learn something entirely new before they can start really contributing. You also have no idea how long it will be supported by its developers into the long term future.
A battle hardened, production tested tool that has a huge community, has been around for a long time, and that a lot more developers already know how to use.
Sure #2 might be slower by a few fractions of a second, but if I’m in charge of the business i know which option I’m going to choose 100% of the time.
lemme guess, Electron
Genuine question, why does it matter? Why shouldn’t a project choose a production ready method of creating cross platform compatible code to avoid duplication of efforts and cost?
Because when I’m looking for where all my RAM went and realise I’m running 7 instances of Chrome browser for no reason. Meanwhile an actual instance of Chrome with ~20 tabs is still a single instance, but with multiple threads.
because most people use more than one program at the same time? fire up that one along with, I dunno, Spotify and Discord and Slack, and suddenly your midrange laptop’s RAM is all but gone.
Same thing happens to me if I were to open each of those apps as chrome tabs.
The apps you listed provide a web version also. Adding choice to the customer experience is a good thing!
deleted by creator
Because many users often enjoy using a dedicated application than a website. Plus it gives developers access to even more customization than browsers normally provide.
If they customers didn’t like using it, companies wouldn’t keep making these apps.
Personally, I’m a techie guy but I get exhausted with the number of tabs i have open at any time. I don’t need to have more dedicated to just slack, Spotify, discord etc
Oh the fact it’s cross platform is not the issue, the issue is that Electron sucks. There are better alternatives available like Tauri, yet companies keep using Electron because that’s what their developers know and they’re afraid to try something new.
If I’m a company and want to bring something to production quickly, what should i choose:
A relatively new tool that has seen barely any production use and thus could have a bunch of unanticipated problems. Also nobody uses it so every new engineer you bring onto the project has to learn something entirely new before they can start really contributing. You also have no idea how long it will be supported by its developers into the long term future.
A battle hardened, production tested tool that has a huge community, has been around for a long time, and that a lot more developers already know how to use.
Sure #2 might be slower by a few fractions of a second, but if I’m in charge of the business i know which option I’m going to choose 100% of the time.