because they don't need to. Our phones and computers aren't where they were 10~15 years ago. The end user doesn't even notice if an app is native or running in Electron.
Given that constraint, time to market becomes crucial as the huge cross platform barrier is significantly reduced by Electron.
It's also a demographic shift. Young developer's aren't coding in Java peak world anymore. We haven't even reached peak Javascript yet.
Definitely a demographic shift. And maybe business smart: cheaper to hire and onboard web devs etc. But that doesn't mean the company and its product shouldn't be critiqued for its architecture (even more so because it is a software company).
> I can see someone is downvoting comments that doesn't agree with time to market being an important driver in influencing architectural decisions. This is someone who is very mature and well seasoned in Java architecture.
Ah yes. Someone who downvotes you, which you assume to be about the time to market comment of your argument, must naturally be a person "who is very mature and well seasoned in Java architecture".
What does that even mean to be "well seasoned in Java architecture"?
Given that constraint, time to market becomes crucial as the huge cross platform barrier is significantly reduced by Electron.
It's also a demographic shift. Young developer's aren't coding in Java peak world anymore. We haven't even reached peak Javascript yet.