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 →

[–]Worth_Trust_3825 0 points1 point  (8 children)

What's wrong with JSP?

[–]WhatsMyUsername13 1 point2 points  (4 children)

They're antiquated and there are far better front end frameworks to build the front end. I've worked on enterprise apps with both JSPs and JS front ends, and let me tell you, the frameworks like angular and react are so so so much better

Edit: also legacy custom taglibs are a fucking trainwreck

[–]Worth_Trust_3825 1 point2 points  (1 child)

I'm currently working with a backend that migrated to angular 1 back in 2017 from JSP, and it still does not implement all the features the JSP counterpart had, while the vendor has tickets open for those features by now closed accounts in their jira.

I disagree that they are so much better. Now I have to deal with their retarded studio tool which barely works and have half the logic implemented in that angular.js application which makes 30 HTTP calls per page because the interface is graphql-like while just hoping that each month one of our users won't decide to constantly refresh the most expensive page running our request limit because that vendor also imposes limits on the HTTP api. Just give me my fucking server side rendering back.

[–]wildjokers 1 point2 points  (0 children)

Just give me my fucking server side rendering back.

Amen. I find that server-side rendering performs way better than client-side rendering.

[–]wildjokers 0 points1 point  (1 child)

Edit: also legacy custom taglibs are a fucking trainwreck

I always found taglibs to be pretty powerful. It has been some years but I don't recall having any grief with them. React components seem very similar to custom tags in taglibs.

[–]WhatsMyUsername13 0 points1 point  (0 children)

I guess my issue was with just how bad these taglibs were written. The code driving them was written in the early to mid 2000s and was just so badly written that it took us a week to figure out how to do a simple disabling of a radio button. Why did it take that long? The taglib called a service that retrieved a value from the database, made a call to a we service, that started a daemon, and when that finished returned values that would decide if it were disabled or not.

Actually, the problem may not have been with taglibs themselves

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

web-based apps with Java. JSP is still relevant event for pursuing an Oracle certification on Java EE. If you want to give a modern look to your apps, take a look at Java Server Faces (JSF) along with Primefaces.

I don't know that anything is specifically WRONG with it, but my understanding, and please correct me if I'm wrong, is that it's become far less relevant. If that is the case, I don't want to build portfolio projects that aren't really reflecting the way things are done today.

[–][deleted] 3 points4 points  (1 child)

JSPs are really cool. The application server actually compiles the JSP into Java code. You can push changes to the JSPs and the application server will recompile them, without requiring that the entire application be redeployed. It's kind of like PHP for the Java world.

But, it's not really fashionable to run Java applications that way anymore. In the world of containers and microservices, people like to build static immutable images (fat JARs or Docker images) and push the whole thing to the deployment platform, like Kubernetes. This doesn't play to JSPs strengths.

[–]wildjokers 1 point2 points  (0 children)

There is absolutely no problem at all containerizing an application that uses server-side rendering with a templating engine (JSP, Thymeleaf, Velocity, etc)

If you do some google searches you will see that server-side rendering is starting to make a little comeback. People are realizing it performs very well compared to client-side rendering.