Re:Java EE Is Moving to the Eclipse Foundation
by pjmlp on Wednesday September 13, 2017 @01:13PM
(#15240347)
When we talk about rich libraries we mean actual libraries for generating PDFs, reading barcodes, report generation, talking with all kinds of enterprise databases, GPU programming, parallel distributed algorithms, embedded development...
Not yet another packaging tool or fait-divers like pad left.
And the majority of them written in pure Java, not C++ wrapped in a JavaScript API.
Re:Java EE Is Moving to the Eclipse Foundation
by tannhaeuser on Wednesday September 13, 2017 @01:35PM
(#15240572)
> When we talk about rich libraries we mean actual libraries for generating PDFs
I was specifically talking about web libraries/tools, though. Nobody is saying Java backend development must be abandoned in general.
Re:Java EE Is Moving to the Eclipse Foundation
by pjmlp on Wednesday September 13, 2017 @02:08PM
(#15240921)
How do you generate a PDF on such a cool JavaScript front end application?
Hint, you don't. Just hope that the browser does a good job with print to PDF, or run a server side pile of shell scripts, using LaTeX and Postscript, instead of a plain simple library.
And this is just one example from many, where JavaScript/Web sucks on the front-end.
Also Android is front-end development.
React, Webpack, CSS compilers and pretty much all other modern frontend (compile-time) asset tools are running on Node.js and install from npmjs.com. Node.js is also perfect for a shallow web-facing container developed along with the front-end as a complement to Java-based (mini/SOA/whatever)-services. So I think it's quite useful to make Node.js workloads run under the JVM.