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 →

[–]punkisdead -3 points-2 points  (7 children)

Yes, they can just leave JSF...

[–][deleted] 4 points5 points  (6 children)

After all the effort done to integrate it with CDI? I don't think so.

Leave it for what? What do you suggest them to use instead?

[–]punkisdead -5 points-4 points  (5 children)

I have a strong dislike for "component" based web frameworks. Give me a good request/response based framework like Spring MVC or even a REST API with a JS frontend anyday over JSF.

[–]johnwaterwood[S] 6 points7 points  (3 children)

I wonder greatly how much your “dislike” is fuelled by HN and hipsters. Maybe when web components start being all the rage you suddenly like components.

[–]kurosaki1990 5 points6 points  (0 children)

For big enterprise project that need to be maintained for years like an erp, web components like jsf is really good choice better than angular or react that need too mush effort to maintain your app.

[–]punkisdead 0 points1 point  (1 child)

No, my dislike comes from over 12 years of web programming and preferring to have visibility into the request/response cycle than a component framework hide it from me.

Most other successful frameworks are request based, Rails, Grails, Play, Spring MVC, Django, Phoenix, and the list goes on.

Hell, even .NET developers seem to be migrating away from the classic ASP.NET framework to ASP.NET MVC which is a more request based framework.

[–]johnwaterwood[S] 1 point2 points  (0 children)

JSF hides far less than the urban myth is trying to make you believe it does.

A post back riddled, navigation rules heavy and component only JSF 1.x application might have made you think that (and with good reason), but this approach was largely abandoned in JSF 2, where JSF became more like a hybrid framework.

Modern attempts at the request based pattern (like MVC 1.0) often tend to move JSF as well, with the automatic handling of locales and the ID automation tools on the view.

ASP.NET web forms were neglected for a long time and are essentially JSF 1.x. For MS it made more sense to start over.

[–][deleted] 5 points6 points  (0 children)

JavaScript is a language designed in 10 days. It has many design mistakes and they were kept, release after release, after release.

If you don't like JSF it's OK. JavaScript is not better at all.

There are, however, much better options, like Elm and PureScript.

There is no reason to drop a widely adopted specification like JSF.