Is there a future for Java on the (Web) Front End?

In a time long ago, developers considered Java for web applications. From the days of building applets and JSP pages, Java has been left behind by new frameworks which adopted new techniques. Java Server Pages (aka JSP) was first introduced in 1999. JSP quickly became the preferred way to developing interactive HTML web pages, you could still use a servlet to generated HTML, but I would not recommend. In 2003, Sun (remember these guys?) released JavaServer Faces; thus, they pushed for it as the preferred way to build dynamic data-driven web sites.

Fast forward to 2020; JavaScript frameworks dominate web application development on the front end. Java is relegated to the server-side. JSF 2.3 updated the support for HTML 5 and WebSocket but it feels as if JSF is still missing something to be cool.

I caught up with Java Champion Cagatay Civici. For those who do not know him, Cagatay is the creator of Primefaces, the most popular JSF UI components compatible with HTML5. Cagatay discussed some of the shortcomings, such as:

– JSF views are not stateless; a standard error is the view expired exception

– JSF is predominantly server-side, even though this could be positive, it has his downside.

I will keep it short so as not to give too much away from his interview on the #OffTheChain podcast.

Watch the video to found out where is sees JSF heading to stay relevant; things like web components, WebAssembly and a quick comparison to Microsoft Blazor.

Happy watching and please leave a comment.

Add a Comment

You must be logged in to post a comment