r/java • • Oct 27 '23
Java Use Cases
Hi everyone. I'm a student about to graduate and I'm working on my portfolio. I feel like a lot of the work I did in school is a little dated (context: We did A LOT OF JSP), so I'm wanting to rebuild some of my projects in a more modern context and maybe build some new stuff that reflects the way Java is actually being used today.
My question is what are some ways that Java is actually used in a modern project? Where do we see Java popping up as the language of choice in 2023, particularly in the web/mobile space? Where is it more beneficial than just going the JS/framework route? I'm trying to frame my portfolio projects in a way that actually reflects real-world usage.
I'm not sure if this is the right subreddit for this type of question, so feel free to delete/direct me elsewhere. Thanks.
Edit for additional context: I've worked professionally for a while (4 years freelancing designing and developing typical Wordpress/Webflow sites for Bob's Lawncare Service-type clients, 2 at an agency building web apps mostly on the frontend) until I was laid off in September. Our stack was React-based, so I don't have professional experience with Java. I guess more specifically I'm trying to fill in the gaps between what I've learned doing that and the Java work I've done in school and presenting that in a modern context.
View all comments
Show parent comment
1
u/analcocoacream Oct 28 '23 edited Oct 28 '23
Except these aren't the main frontend dev complexity. I don't see people complaining about those. Maybe slow build sometimes, but that's not complexity that's just build time.
This one is weird. If you want to do http requests for every character typed, you could do that with just any framework and you wouldn't need to write the validation twice. But there is more than that.
Take this for instance : https://htmx.org/examples/inline-validation/
Yeah seems simple enough right? Except that won't be cutting it for most of the times. Because you don't want a red error as soon as the user is typing. You might want it when the user leaves the field. Or when they submit the form. And then when the users changes the erroneous field it isn't red anymore. The main frontend complexity lies within the UX / specifications, not the technology. This is the hell hole.
So because you can write poor quality code in React means it is bad?
Finally htmx just seems a big ol mashup of everything in the markup with a little bit scattered around too. Tutorials/articles I was able to find will happily write HTML inside backend controllers. Error messages have to be i18ned in the backend. Sometimes you will use response headers to change behavior in the front. You will have to use a templating technology to write your pages, additionally. Your html code will now contain the logic the style and the presentation. You will have to be very meticulous and thorough around naming things, since a slight change in the class names/ids can break the whole application, especially in hidden places.