6 ms·
> Can someone explain what Java EE really means? I tried to parse the bundle and license the last time this came up, and I didn't really get anywhere. It's no
by camus2 9y ago
> Can someone explain what Java EE really means? I tried to parse the bundle and license the last time this came up, and I didn't really get anywhere.
It's no different than Web standards between browsers, it's a collection of API specifications describing how web applications should be architectured in Java. Then different libraries can follow the spec. JavaEE also has a reference implementation which used to be done by Sun/Oracle.
The problem with JavaEE is, by being too broad and generic, it is incredibly complex and often fails to solve today's developers problems. I mean who cares about JSF(java server face, a way to describe "HTML GUI widgets" in XML) when most applications use a RESTful architecture? Beans session persistance? ... JEE has a lot of technical debt, the word is definitely appropriate here.
- xienze 9y ago> I mean who cares about JSF(java server face, a way to describe "HTML GUI widgets" in XML) Well, a lot of people did because once upon a time that's how we wrote applications (primarily via server-side rendering). > when most applications use a RESTful architecture? Java EE has an API for that... > JEE has a lot of technical debt Can't argue with that, but it comes in the form of APIs you don't have to use.
- pjmlp 9y agoMost enterprise shops do care about JSF. I know of many greenfield projects using it, mainly PrimeFaces.
- tannhaeuser 9y agoThey do for legacy apps only, though, since JSP, JSF and everything on top of it, such as portlets and faces component libs, has been obsolete for many years now. Handling UI state on the server just doesn't make any technical sense when there are React, Angular and Co as mainstream GUI kits. I guess there are still those shops maintaining intranet apps, and for whom it is a priority that everything is 100% Java, or who can't or don't want to invest into JavaScript or another web stack, but I think a responsible consultant should tell these customers that their stack is on life support now.
- cjsuk 9y agoA lot of enterprise companies aren't buying in JS frameworks because the velocity of those frameworks is too fast. I kind of agree. When you have 50,000 desktops, a 6 month lead dragging a pile of apps over to a new browser is a nightmare scenario. All it takes is one app which the vendor doesn't give a shit about and one internal app deprecating an IE version used by 50 users due to a JS framework change in a branch office and there's a headache from hell on your plate. Fortunately they're all starting to kick out chrome for business now.
- tannhaeuser 9y agoMaybe for those customers it might make sense to donate to the Eclipse foundation to keep JSF etc. alive and to keep Java-only devs afloat? But then maintenance of J2EE has ceased because it's not economically feasible.
- cjsuk 9y agoIt probably would but it won't happen. It's difficult getting anything like that through the layers of purchasing hell. If they provided a web site with pictures of boxes of software for min $2000 that never arrived and didn't do anything it might work better. The moment someone says "donate" the bean counters start sharpening their pitchforks.
- pjmlp 9y agoWe have customers were using Chrome is a security risk, because they cannot control its deployments like on FF, IE and Edge.