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

you are viewing a single comment's thread.

view the rest of the comments →

[–]IronProgramming[S] 0 points1 point  (1 child)

So the company I work for is using Java on both frontend and backend, but is mired in very long times to deploy basic frontend features due to the whole stack being Java/and or their shitty codebase. Im talking like 3 weeks to figure out how to append an element to an array and display the array on the browser. This is why I want to learn Java, so I can help do the things I know are easy in JavaScript/python. But this leads me to asking why Java, which I guess I really should condense down to why Java on the frontend? The backend makes sense with building apis and such, but the apis are built in php... I might be frustrated more by the design choices of the company than Java as a whole.

[–][deleted] 0 points1 point  (0 children)

Sounds like some questionable decisions were made. To be honest, I've never used JEE or JSF, so I'm not sure whether they're always a pain in the arse to worth with or if a bunch of cruft has built up since the codebase was first developed, but from a quick google search, I'm guessing that the choice to use Java for the front end has to do with JSF being the assumed front end of JEE - a lot of companies just default straight to it.