All very nice with HTML UI and the browser, but what about standalone apps that need near real time performance. They cannot count on the browser and on Javascript I 'm afraid. They need Swing and/or JavaFX or something similar.
If this is the case with the Java kingdom, then all these apps will move to other technologies that take advantage of the new hardware and the GPUs. Regards, John. On 12 March 2018 at 17:25, Neil C Smith <neilcsm...@apache.org> wrote: > On Mon, 12 Mar 2018 at 15:59 Jaroslav Tulach <jaroslav.tul...@gmail.com> > wrote: > > > Forget about AWT, Swing and JavaFX - the future is HTML. In case you > still > > care about Java, then your future should be Apache HTML/Java API! > > > > Generally inclined to agree with you - definitely on forgetting JavaFX, and > probably on forgetting AWT/Swing (intrigued to see what actually happens > there). I don't think HTML is the only game in town, but for a lot of > things it's probably the right way forward. > > But, if we start turning to Apache HTML/Java way, what does it run in? > > Out of interest, I was looking at an example project using Vaadin running > inside Electron recently. Have you tried this approach with HTML/Java? > > Best wishes, > > Neil > -- > Neil C Smith > Artist & Technologist > www.neilcsmith.net > > Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org >
