[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ee4j-community] Red Hat committment to EE4J
|
While I am sure the community can pick some things up just like they did for Java EE 8, the reality is probably that most folks are just like me - we will try to do what we can when the demands of the day job (the stuff that actually helps pay the bills) and family (the stuff that actually really matters at the end of the day) is done. Realistically, this probably means about 15-20 hours a week on good weeks.
What this means is that if this effort is to be in any way competitive, vendors will still need to do a lion's share of the work much like is the case for Spring, the Lightbend stack, etc. The secret sauce for Spring in particular is that Pivotal has no hesitation investing in the Spring stack even when they do not directly make money from it. If vendors do not have the similar mindset here, I agree it's wise to stop wasting any more effort, throw in the towel now and move on to bigger and better things. While an effort driven mostly by community can move forward for shorts bursts of time, the reality is that it is no match for professionals getting paid full time to do 50-60 hours of work each week.
Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
-------- Original message --------
From: Mark Little <mlittle@xxxxxxxxxx>
Date: 10/16/17 8:06 AM (GMT-05:00)
To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>
Subject: Re: [ee4j-community] Red Hat committment to EE4J
More specifically, is Red Hat going to continue to move CDI and Bean Validation forward?
Yes, where forward movement makes sense.
What about JPA? I don't think anyone in the community can realistically move that forward. I have similar concerns for Servlet (and perhaps a more reactive alternative to Servlet). These APIs are so complex that you really need dedicated folks that work for a vendor full time to move them forward.
We will remain active in other JSRs and help with new efforts where it makes sense. But the community has to also step forward and help make this a success because if it remains solely in the hands of the vendors then maybe we should just roll everything back.
-------- Original message --------
Date: 10/12/17 7:44 AM (GMT-05:00)
Subject: Re: [ee4j-community] Red Hat committment to EE4J
Mark,
For the avoidance of doubt and for those who haven't been paying
attention :) Red Hat is committed to working for the continuing
success of Java EE and now EE4J. We intend to put forward various
individuals who may be relevant to lead various JSRs if no other
appropriate community members step forward as well as the JSRs we lead
currently. When the time is right (note, when not if) we'll also work
to ensure EE4J and Eclipse MicroProfile collaborate in a meaningful
manner and hopefully "merge" in whatever way is appropriate and
determined by both communities.
I'm assuming that the last "we" here is the MicroProfile community and not RedHat, correct?
Mark.
_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community
_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community
---
Mark Little
JBoss, by Red Hat
Registered Address: Red Hat Ltd, 6700 Cork Airport Business Park, Kinsale Road, Co. Cork.
Registered in the Companies Registration Office, Parnell House, 14 Parnell Square, Dublin 1, Ireland, No.304873
Directors:Michael Cunningham (USA), Vicky Wiseman (USA), Michael O'Neill, Keith Phelan, Matt Parson (USA)
