IMHO, it's far from dead, but it's losing ground for sure.
The JavaEE specification and APIs can eliminate the need for maintaining Maven dependencies, which can be a security liability if you don't know how to avoid insecure JARs from being compiled into your web application. Imagine building a robust web app using only the standard library of your programming language of choice so you don't need external dependencies (or very few): that's the use case JavaEE is best intended for.
The Eclipse MicroProfile specification within JavaEE is an attempt at giving JavaEE a second wind as well, given the popularity of microservice architectures.
IMHO, it's far from dead, but it's losing ground for sure.
The JavaEE specification and APIs can eliminate the need for maintaining Maven dependencies, which can be a security liability if you don't know how to avoid insecure JARs from being compiled into your web application. Imagine building a robust web app using only the standard library of your programming language of choice so you don't need external dependencies (or very few): that's the use case JavaEE is best intended for.
The Eclipse MicroProfile specification within JavaEE is an attempt at giving JavaEE a second wind as well, given the popularity of microservice architectures.
Thank you, this is the very first time that I hear about Eclipse MicroProfile.