3 ms·
The problem with the JVM is that the UI toolkits are dying or died already. Having the web as UI layer brings much benefit and reduces the investement needed i
by hexa00 9y ago
The problem with the JVM is that the UI toolkits are dying or died already. Having the web as UI layer brings much benefit and reduces the investement needed in the UI.
IDEA will most likely hit that problem at some point also...
- stephenr 9y agoJetBrains apps look & behave mostly native on macOS. There are some discrepancies, but they're pretty close. Building the entire UI in a webview means you're never going to get platform integration. No standard menu bar, no services integration, no remapping menu shortcut keys, no automatic "find command" in the Help menu. Edit: s/look/look & behave/
- hexa00 9y agoThat's not entierly true since Electron provides native elements like menus for example. We can hope Electron will get better at a native experience and can contribute to that too. See https://electron.atom.io/docs/tutorial/desktop-environment-integration/ https://electron.atom.io/docs/tutorial/desktop-environment-i...
- TeMPOraL 9y ago> The problem with the JVM is that the UI toolkits are dying or died already. Wait, what? I'm pretty sure native UI toolkits are holding up fine. They did fall off the hipster train, true, but that doesn't mean they're dying. On JVM, maybe it's time to retire Swing, but JavaFX is alive and kicking.
- hexa00 9y agoI could be wrong but I don't see JavaFX as alive and kicking... Especially compared to web technologies. And it's tied to Oracle pretty much...
- jameskegel 9y agoNo need for name calling; you both have your points.