|Re: [jakartaee-platform-dev] Specification backward compatibility requirements|
Wow, really. I'm speechless.
Do the people who decide such things IN THE DARK (aka undocumented it seems) mean this serious?
I mean, really this got nowhere made public, was it? Please point me to the articles covering this!
That would imo TOTALLY ditch the whole purpose of JavaEE / JakartaEE in my eyes.
If a project wants to use quickly evolving technologies, then they do usually NOT choose JavaEE.
JavaEE - in my experience - was previously chosen by companies and governmental organisations whose primary goal is stability over a very long period of time. We are talking in 5 to 10 years of stability. Now when you folks ditch this, then I fear we will loose banks, governments, etc. Those 'slow moving dinosaurs' in my experience used to be the main users of JavaEE. They provide the main money, they have the most code running in JavaEE.
There is a good reason why people used to say "JavaEE is these days COBOL". That's because COBOL apps are running till today. Like many JavaEE apps I see at customers. Many of them older than 10 years, but still perfectly maintainable.
And for container vendors: why should I pass a TCK if the rules are totally turned around in 2 years anyway? I mean this is a joke, really :(
PS: Scott, I understand you are just the messenger, so no personal offense meant.
Back to the top