Because more often than not good enough is good enough. Electron is a great example. Look at the market share of slack, discord, spotify, etc.
Optimizing as step one is a very good way to not ship on time and miss opportunities to competition.
Optimizing as step one is a very good way to not ship on time and miss opportunities to competition.
what gets considered important are things that hurt them rather than their users. In many ways it's an abuse of users.
But when 3 of these bulky apps are eating the whole RAM and no more software can run because of them, it's the user, especially the not very savvy user, the one who usually assumes their computer doesn't work any more for modern software and they need to incur in the effort and cost of acquiring a new one.
Electron is a fine way to test a market, but it is only financially viable to use long term (such as done by Slack, Discord or Spotify) because it externalizes the actual cost to its users.
For an app that is open-use-close, it's ok and I see no issue. But for apps meant to be constantly running in the background (like a music player or a chat app) I think Electron is almost a sin against its users.
But they’ve determined that this cost isn’t meaningful enough to write performant native platform specific versions.
That obviously sucks for your users who really need it, but if there aren’t many of them, the site/app/whatever will just be hard to use for them, probably forever.
thank you
I hate "ally" thing so much >_<
On the initial use of an unfamiliar acronym within a document or a section, spell out
the full term, and then put the acronym in parentheses.
In a non-tech specific community, I wouldn’t use these abbreviations, but I see no issue with them here.