3 ms·
I would agree if the goal is just to build a web app, however, if you want to run natively on multiple platforms, Java still has its good points. If you really
by jeffreportmill1 8y ago
I would agree if the goal is just to build a web app, however, if you want to run natively on multiple platforms, Java still has its good points. If you really run a particular app on a daily basis, it can be nice to have an option for a dedicated desktop app.
We may see more of this with WASM. And JavaScript can get a little unwieldy beyond 100k lines of code.
- giornogiovanna 8y agoI don't know if such a thing exists yet, but how would Java compare to a shared Electron? [ Found the issue. https://github.com/electron/electron/issues/673 https://github.com/electron/electron/issues/673 ]
- drderidder 8y agoIt's those multi-client scenarios for which the API-first approach is a perfect fit, actually. Once the API is hammered out, it forms the common foundation for building gui's, cli's and even machine-to-machine interfaces. As a stepping stone, web applications can be deployed as hybrid mobile apps using something like Apache Cordova, even as fully native apps for Android and iOS are under development. Once you've implemented something like this, it's hard to go back to monolithic codebases. Caveat: this is predicated on having an API server and requiring an Internet connection. Writing a connectionless app this way would require some additional effort, though still quite do-able.