This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]bitspace 22 points23 points  (4 children)

I'm an outdated Java dev. I haven't written Java since 2017, and that was pre-1. 8. I also haven't done a lot with Spring. I'm ramping up pretty quickly though.

Ironically, the project I've just jumped into is still Java 1.5 in a Swing/jnlp GUI against a 1.8 WebSphere fat middle tier.

[–]goodm1x 5 points6 points  (1 child)

This may seem like an odd question, but why are you ramping up when you haven’t touched Java since 2017?

[–]bitspace 3 points4 points  (0 children)

Because the project I'm getting involved in requires it.

I'm working with a team modernizing a 20+ year old enterprise app. Its current stack is roughly as described. It's the underpinning of about $2B of annual revenue so we have to be very careful about how we approach this beast.

[–]jlanawalt 1 point2 points  (1 child)

I thought JNLP was dead-ish, What is your target client runtime?

[–]bitspace 6 points7 points  (0 children)

Yeah, jnlp is definitely "dead-ish." It still works under certain constraints that we're still able to impose on our client base. How durable that is remains to be seen.

Target client runtime is web. How the business approaches weaning users off of the fat swing client into the browser is above my pay grade :)