Skip to content

Instantly share code, notes, and snippets.

@nekman

nekman/jsf.md

Last active June 19, 2020 10:41
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save nekman/8774761 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save nekman/8774761 to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. nekman revised this gist Jun 12, 2014. 1 changed file with 2 additions and 3 deletions.
    5 changes: 2 additions & 3 deletions jsf.md
    View file
    Original file line number Diff line number Diff line change
    @@ -16,6 +16,5 @@ http://java.dzone.com/articles/why-java-ee-lost-and-spring - Interesting read ab
    >Server-managed state began as a workaround for browsers that couldn’t hold state, where each page was re-rendered and cut from whole cloth. Later, with XMLHttpRequest/AJAX, browsers could manage state, but server-managed state was still used because of how much simpler it was to code (until you have a lot of it and the server crashes). Server-managed state has become a monster and complexity is being manufactured.

    http://ptrthomas.wordpress.com/2009/05/15/jsf-sucks - Classic!<br>
    http://ihatejsf.com - Classic!<br>
    http://gokhan.ozar.net/wp-content/uploads/jsf.jpg - Word!<br>
    http://ptrthomas.wordpress.com/2009/05/15/jsf-sucks<br>

  2. nekman revised this gist Feb 4, 2014. 1 changed file with 3 additions and 3 deletions.
    6 changes: 3 additions & 3 deletions jsf.md
    View file
    Original file line number Diff line number Diff line change
    @@ -7,9 +7,6 @@ http://www.jfokus.se/jfokus/talks.jsp - Search for JSF... (one hit on why you sh
    http://architecture-musings.blogspot.se/2012/01/jsf-dead-on-arrival.html<br>
    >Server side UI rendering and lack of client-side scripting ensures that JSF will not succeed as the paradigm has shifted. You will hear of many improvements in JSF 2.0, but I am not looking.

    http://ptrthomas.wordpress.com/2009/05/15/jsf-sucks - Classic!<br>
    http://ihatejsf.com - Classic!<br>
    http://www.youtube.com/watch?v=9ei-rbULWoA#t=47m - James Gosling about JSF<br>
    http://java.dzone.com/articles/j2ee-dead-long-live-javascript<br>
    >This enables our front-end developers to be *incredibly* productive. They don't need to run a server of any kind. We stub out the JSON services with flat files, and they can plow ahead, cranking out kick-ass look and feel and slick UX. To be honest, they probably haven't heard the acronym J2EE. (and probably never will)
    @@ -18,4 +15,7 @@ Meanwhile, back at the (server) farm, our java-heads can crank out light-weight
    http://java.dzone.com/articles/why-java-ee-lost-and-spring - Interesting read about JSF and Java EE<br>
    >Server-managed state began as a workaround for browsers that couldn’t hold state, where each page was re-rendered and cut from whole cloth. Later, with XMLHttpRequest/AJAX, browsers could manage state, but server-managed state was still used because of how much simpler it was to code (until you have a lot of it and the server crashes). Server-managed state has become a monster and complexity is being manufactured.

    http://ptrthomas.wordpress.com/2009/05/15/jsf-sucks - Classic!<br>
    http://ihatejsf.com - Classic!<br>
    http://gokhan.ozar.net/wp-content/uploads/jsf.jpg - Word!<br>
  3. nekman revised this gist Feb 4, 2014. No changes.
  4. nekman revised this gist Feb 3, 2014. 1 changed file with 3 additions and 0 deletions.
    3 changes: 3 additions & 0 deletions jsf.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,4 +1,7 @@
    ### JSF?!
    http://www.thoughtworks.com/radar/#/languages-and-frameworks/683 - ThoughtWorks Technology Radar - January 2014<br>
    >We continue to see teams run into trouble using JSF -- JavaServer Faces -- and are recommending you avoid this technology. Teams seem to choose JSF because it is a J2EE standard without really evaluating whether the programming model suits them. We think JSF is flawed because it tries to abstract away HTML, CSS and HTTP, exactly the reverse of what modern web frameworks do. JSF, like ASP.NET webforms, attempts to create statefulness on top of the stateless protocol HTTP and ends up causing a whole host of problems involving shared server-side state. We are aware of the improvements in JSF 2.0, but think the model is fundamentally broken. We recommend teams use simple frameworks and embrace and understand web technologies including HTTP, HTML and CSS.
    <br>
    http://www.jfokus.se/jfokus/talks.jsp - Search for JSF... (one hit on why you should leave it)<br>
    http://architecture-musings.blogspot.se/2012/01/jsf-dead-on-arrival.html<br>
  5. nekman revised this gist Feb 2, 2014. 1 changed file with 2 additions and 2 deletions.
    4 changes: 2 additions & 2 deletions jsf.md
    View file
    Original file line number Diff line number Diff line change
    @@ -5,8 +5,8 @@ http://architecture-musings.blogspot.se/2012/01/jsf-dead-on-arrival.html<br>
    >Server side UI rendering and lack of client-side scripting ensures that JSF will not succeed as the paradigm has shifted. You will hear of many improvements in JSF 2.0, but I am not looking.

    http://ptrthomas.wordpress.com/2009/05/15/jsf-sucks - Classic!/<br>
    http://ihatejsf.com - Klassiker/<br>
    http://ptrthomas.wordpress.com/2009/05/15/jsf-sucks - Classic!<br>
    http://ihatejsf.com - Classic!<br>
    http://www.youtube.com/watch?v=9ei-rbULWoA#t=47m - James Gosling about JSF<br>
    http://java.dzone.com/articles/j2ee-dead-long-live-javascript<br>
    >This enables our front-end developers to be *incredibly* productive. They don't need to run a server of any kind. We stub out the JSON services with flat files, and they can plow ahead, cranking out kick-ass look and feel and slick UX. To be honest, they probably haven't heard the acronym J2EE. (and probably never will)
  6. nekman created this gist Feb 2, 2014.
    18 changes: 18 additions & 0 deletions jsf.md
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,18 @@
    ### JSF?!
    <br>
    http://www.jfokus.se/jfokus/talks.jsp - Search for JSF... (one hit on why you should leave it)<br>
    http://architecture-musings.blogspot.se/2012/01/jsf-dead-on-arrival.html<br>
    >Server side UI rendering and lack of client-side scripting ensures that JSF will not succeed as the paradigm has shifted. You will hear of many improvements in JSF 2.0, but I am not looking.

    http://ptrthomas.wordpress.com/2009/05/15/jsf-sucks - Classic!/<br>
    http://ihatejsf.com - Klassiker/<br>
    http://www.youtube.com/watch?v=9ei-rbULWoA#t=47m - James Gosling about JSF<br>
    http://java.dzone.com/articles/j2ee-dead-long-live-javascript<br>
    >This enables our front-end developers to be *incredibly* productive. They don't need to run a server of any kind. We stub out the JSON services with flat files, and they can plow ahead, cranking out kick-ass look and feel and slick UX. To be honest, they probably haven't heard the acronym J2EE. (and probably never will)
    Meanwhile, back at the (server) farm, our java-heads can crank out light-weight services, which replace the stub JSON files with real services that interact with the back-end systems. T

    http://java.dzone.com/articles/why-java-ee-lost-and-spring - Interesting read about JSF and Java EE<br>
    >Server-managed state began as a workaround for browsers that couldn’t hold state, where each page was re-rendered and cut from whole cloth. Later, with XMLHttpRequest/AJAX, browsers could manage state, but server-managed state was still used because of how much simpler it was to code (until you have a lot of it and the server crashes). Server-managed state has become a monster and complexity is being manufactured.
    http://gokhan.ozar.net/wp-content/uploads/jsf.jpg - Word!<br>