Alternatives to JSF logo

Alternatives to JSF

AngularJS, Spring MVC, Spring, Vaadin, and HTML5 are the most popular alternatives and competitors to JSF.
118
188
+ 1
4

What is JSF and what are its top alternatives?

It is used for building component-based user interfaces for web applications and was formalized as a standard through the Java Community
JSF is a tool in the Javascript MVC Frameworks category of a tech stack.

Top Alternatives to JSF

  • AngularJS
    AngularJS

    AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML’s syntax to express your application’s components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding. ...

  • Spring MVC
    Spring MVC

    A Java framework that follows the Model-View-Controller design pattern and provides an elegant solution to use MVC in spring framework by the help of DispatcherServlet. ...

  • Spring
    Spring

    A key element of Spring is infrastructural support at the application level: Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments. ...

  • Vaadin
    Vaadin

    It is the fastest way to build web applications in Java. It automates the communication between your server and the browser and gives you a high-level component API for all Vaadin components ...

  • HTML5
    HTML5

    HTML5 is a core technology markup language of the Internet used for structuring and presenting content for the World Wide Web. As of October 2014 this is the final and complete fifth revision of the HTML standard of the World Wide Web Consortium (W3C). The previous version, HTML 4, was standardised in 1997. ...

  • JavaFX
    JavaFX

    It is a set of graphics and media packages that enables developers to design, create, test, debug, and deploy rich client applications that operate consistently across diverse platforms. ...

  • PrimeFaces
    PrimeFaces

    It is a popular open source framework for JavaServer Faces featuring over 100 components, touch optimized mobilekit, client side validation, theme engine and more. ...

  • React
    React

    Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project. ...

JSF alternatives & related posts

AngularJS logo

AngularJS

48.5K
36.1K
5.2K
Superheroic JavaScript MVW Framework
48.5K
36.1K
+ 1
5.2K
PROS OF ANGULARJS
  • 887
    Quick to develop
  • 587
    Great mvc
  • 572
    Powerful
  • 521
    Restful
  • 503
    Backed by google
  • 349
    Two-way data binding
  • 343
    Javascript
  • 328
    Open source
  • 305
    Dependency injection
  • 197
    Readable
  • 75
    Fast
  • 64
    Directives
  • 63
    Great community
  • 56
    Free
  • 38
    Extend html vocabulary
  • 29
    Components
  • 26
    Easy to test
  • 24
    Easy to learn
  • 23
    Easy to templates
  • 23
    Great documentation
  • 21
    Easy to start
  • 18
    Awesome
  • 17
    Light weight
  • 14
    Angular 2.0
  • 14
    Javascript mvw framework
  • 13
    Great extensions
  • 13
    Efficient
  • 10
    Easy to prototype with
  • 8
    High performance
  • 8
    Coffeescript
  • 7
    Mvc
  • 7
    Two-way binding
  • 7
    Lots of community modules
  • 6
    Easy to e2e
  • 6
    Clean and keeps code readable
  • 5
    Easy for small applications
  • 5
    One of the best frameworks
  • 4
    Fast development
  • 4
    Works great with jquery
  • 3
    I do not touch DOM
  • 2
    Be a developer, not a plumber.
  • 2
    Declarative programming
  • 2
    Dart
  • 2
    Community
  • 2
    The two-way Data Binding is awesome
  • 2
    Hierarchical Data Structure
  • 2
    Typescript
  • 1
    Botionescu@gmail.com
  • 1
    The powerful of binding, routing and controlling routes
  • 1
    Fkin awesome
  • 1
    Opinionated in the right areas
  • 1
    Supports api , easy development
  • 1
    Common Place
  • 1
    Great
  • 1
    Very very useful and fast framework for development
  • 1
    Amazing community support
  • 1
    Readable code
  • 1
    Linear learning curve
  • 1
    Scopes
  • 1
    Programming fun again
  • 1
    Acoperișul
  • 1
    Consistency with backend architecture if using Nest
  • 0
    Httpș//Acoperișul 0757604335
  • 0
    Angular js
  • 0
    Oautho loc
  • 0
    Shvzjn
  • 0
    Acoperișul 0757604335
  • 0
    Js
  • 0
    Bot Ionescu
  • 0
    Google.com
CONS OF ANGULARJS
  • 10
    Complex
  • 3
    Dependency injection
  • 2
    Learning Curve
  • 2
    Event Listener Overload
  • 1
    Hard to learn

related AngularJS posts

Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 25 upvotes · 2.5M views

Our whole Node.js backend stack consists of the following tools:

  • Lerna as a tool for multi package and multi repository management
  • npm as package manager
  • NestJS as Node.js framework
  • TypeScript as programming language
  • ExpressJS as web server
  • Swagger UI for visualizing and interacting with the API’s resources
  • Postman as a tool for API development
  • TypeORM as object relational mapping layer
  • JSON Web Token for access token management

The main reason we have chosen Node.js over PHP is related to the following artifacts:

  • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
  • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
  • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
  • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
See more
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 22 upvotes · 1.2M views

Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

  • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
  • Vue Styleguidist as our style guide and pool of developed Vue.js components
  • Vuetify as Material Component Framework (for fast app development)
  • TypeScript as programming language
  • Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
  • ESLint, TSLint and Prettier for coding style and code analyzes
  • Jest as testing framework
  • Google Fonts and Font Awesome for typography and icon toolkit
  • NativeScript-Vue for mobile development

The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

  • Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
  • Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
  • Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
  • Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
  • Large scaling. Vue.js can help to develop pretty large reusable templates.
  • Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
See more
Spring MVC logo

Spring MVC

441
453
0
A Java framework which is used to build web applications
441
453
+ 1
0
PROS OF SPRING MVC
    Be the first to leave a pro
    CONS OF SPRING MVC
      Be the first to leave a con

      related Spring MVC posts

      NIDHISH PUTHIYADATH
      Lead Software Engineer at EDIFECS · | 1 upvote · 139.6K views

      Material Design for Angular Angular 2 Node.js TypeScript Spring-Boot RxJS Microsoft SQL Server Hibernate Spring MVC

      We built our customer facing portal application using Angular frontend backed by Spring boot.

      See more
      Spring logo

      Spring

      3.5K
      4.1K
      1K
      Provides a comprehensive programming and configuration model for modern Java-based enterprise applications
      3.5K
      4.1K
      + 1
      1K
      PROS OF SPRING
      • 224
        Java
      • 155
        Open source
      • 133
        Great community
      • 120
        Very powerful
      • 112
        Enterprise
      • 63
        Lot of great subprojects
      • 59
        Easy setup
      • 44
        Convention , configuration, done
      • 38
        Standard
      • 29
        Love the logic
      • 12
        Good documentation
      • 10
        Stability
      • 10
        Dependency injection
      • 7
        MVC
      • 6
        Easy
      • 3
        Strong typing
      • 3
        Makes the hard stuff fun & the easy stuff automatic
      • 2
        Maven
      • 2
        Code maintenance
      • 2
        Best practices
      • 2
        Great Desgin
      • 2
        Easy Integration with Spring Security
      • 2
        Integrations with most other Java frameworks
      • 1
        Java has more support and more libraries
      • 1
        Supports vast databases
      • 1
        Large ecosystem with seamless integration
      • 1
        OracleDb integration
      • 1
        Live project
      CONS OF SPRING
      • 15
        Draws you into its own ecosystem and bloat
      • 3
        Verbose configuration
      • 3
        Poor documentation
      • 3
        Java
      • 2
        Java is more verbose language in compare to python

      related Spring posts

      Is learning Spring and Spring Boot for web apps back-end development is still relevant in 2021? Feel free to share your views with comparison to Django/Node.js/ ExpressJS or other frameworks.

      Please share some good beginner resources to start learning about spring/spring boot framework to build the web apps.

      See more

      I am consulting for a company that wants to move its current CubeCart e-commerce site to another PHP based platform like PrestaShop or Magento. I was interested in alternatives that utilize Node.js as the primary platform. I currently don't know PHP, but I have done full stack dev with Java, Spring, Thymeleaf, etc.. I am just unsure that learning a set of technologies not commonly used makes sense. For example, in PrestaShop, I would need to work with JavaScript better and learn PHP, Twig, and Bootstrap. It seems more cumbersome than a Node JS system, where the language syntax stays the same for the full stack. I am looking for thoughts and advice on the relevance of PHP skillset into the future AND whether the Node based e-commerce open source options can compete with Magento or Prestashop.

      See more
      Vaadin logo

      Vaadin

      156
      221
      34
      Components and tools for building web apps in Java
      156
      221
      + 1
      34
      PROS OF VAADIN
      • 8
        Java
      • 7
        Compatibility
      • 6
        Open Source
      • 5
        Components
      • 3
        Performance
      • 2
        Abstraction
      • 2
        Example packages
      • 1
        OSGI Support
      CONS OF VAADIN
      • 3
        Paid for more features

      related Vaadin posts

      HTML5 logo

      HTML5

      112.4K
      92.3K
      2.2K
      5th major revision of the core language of the World Wide Web
      112.4K
      92.3K
      + 1
      2.2K
      PROS OF HTML5
      • 445
        New doctype
      • 388
        Local storage
      • 334
        Canvas
      • 285
        Semantic header and footer
      • 238
        Video element
      • 120
        Geolocation
      • 105
        Form autofocus
      • 98
        Email inputs
      • 84
        Editable content
      • 79
        Application caches
      • 10
        Easy to use
      • 9
        Cleaner Code
      • 4
        Easy
      • 4
        Semantical
      • 3
        Websockets
      • 3
        Better
      • 3
        Audio element
      • 3
        Modern
      • 2
        Content focused
      • 2
        Compatible
      • 2
        Portability
      • 2
        Semantic Header and Footer, Geolocation, New Doctype
      CONS OF HTML5
      • 1
        Easy to forget the tags when you're a begginner
      • 1
        Long and winding code

      related HTML5 posts

      Jonathan Pugh
      Software Engineer / Project Manager / Technical Architect · | 25 upvotes · 1.7M views

      I needed to choose a full stack of tools for cross platform mobile application design & development. After much research and trying different tools, these are what I came up with that work for me today:

      For the client coding I chose Framework7 because of its performance, easy learning curve, and very well designed, beautiful UI widgets. I think it's perfect for solo development or small teams. I didn't like React Native. It felt heavy to me and rigid. Framework7 allows the use of #CSS3, which I think is the best technology to come out of the #WWW movement. No other tech has been able to allow designers and developers to develop such flexible, high performance, customisable user interface elements that are highly responsive and hardware accelerated before. Now #CSS3 includes variables and flexboxes it is truly a powerful language and there is no longer a need for preprocessors such as #SCSS / #Sass / #less. React Native contains a very limited interpretation of #CSS3 which I found very frustrating after using #CSS3 for some years already and knowing its powerful features. The other very nice feature of Framework7 is that you can even build for the browser if you want your app to be available for desktop web browsers. The latest release also includes the ability to build for #Electron so you can have MacOS, Windows and Linux desktop apps. This is not possible with React Native yet.

      Framework7 runs on top of Apache Cordova. Cordova and webviews have been slated as being slow in the past. Having a game developer background I found the tweeks to make it run as smooth as silk. One of those tweeks is to use WKWebView. Another important one was using srcset on images.

      I use #Template7 for the for the templating system which is a no-nonsense mobile-centric #HandleBars style extensible templating system. It's easy to write custom helpers for, is fast and has a small footprint. I'm not forced into a new paradigm or learning some new syntax. It operates with standard JavaScript, HTML5 and CSS 3. It's written by the developer of Framework7 and so dovetails with it as expected.

      I configured TypeScript to work with the latest version of Framework7. I consider TypeScript to be one of the best creations to come out of Microsoft in some time. They must have an amazing team working on it. It's very powerful and flexible. It helps you catch a lot of bugs and also provides code completion in supporting IDEs. So for my IDE I use Visual Studio Code which is a blazingly fast and silky smooth editor that integrates seamlessly with TypeScript for the ultimate type checking setup (both products are produced by Microsoft).

      I use Webpack and Babel to compile the JavaScript. TypeScript can compile to JavaScript directly but Babel offers a few more options and polyfills so you can use the latest (and even prerelease) JavaScript features today and compile to be backwards compatible with virtually any browser. My favorite recent addition is "optional chaining" which greatly simplifies and increases readability of a number of sections of my code dealing with getting and setting data in nested objects.

      I use some Ruby scripts to process images with ImageMagick and pngquant to optimise for size and even auto insert responsive image code into the HTML5. Ruby is the ultimate cross platform scripting language. Even as your scripts become large, Ruby allows you to refactor your code easily and make it Object Oriented if necessary. I find it the quickest and easiest way to maintain certain aspects of my build process.

      For the user interface design and prototyping I use Figma. Figma has an almost identical user interface to #Sketch but has the added advantage of being cross platform (MacOS and Windows). Its real-time collaboration features are outstanding and I use them a often as I work mostly on remote projects. Clients can collaborate in real-time and see changes I make as I make them. The clickable prototyping features in Figma are also very well designed and mean I can send clickable prototypes to clients to try user interface updates as they are made and get immediate feedback. I'm currently also evaluating the latest version of #AdobeXD as an alternative to Figma as it has the very cool auto-animate feature. It doesn't have real-time collaboration yet, but I heard it is proposed for 2019.

      For the UI icons I use Font Awesome Pro. They have the largest selection and best looking icons you can find on the internet with several variations in styles so you can find most of the icons you want for standard projects.

      For the backend I was using the #GraphCool Framework. As I later found out, #GraphQL still has some way to go in order to provide the full power of a mature graph query language so later in my project I ripped out #GraphCool and replaced it with CouchDB and Pouchdb. Primarily so I could provide good offline app support. CouchDB with Pouchdb is very flexible and efficient combination and overcomes some of the restrictions I found in #GraphQL and hence #GraphCool also. The most impressive and important feature of CouchDB is its replication. You can configure it in various ways for backups, fault tolerance, caching or conditional merging of databases. CouchDB and Pouchdb even supports storing, retrieving and serving binary or image data or other mime types. This removes a level of complexity usually present in database implementations where binary or image data is usually referenced through an #HTML5 link. With CouchDB and Pouchdb apps can operate offline and sync later, very efficiently, when the network connection is good.

      I use PhoneGap when testing the app. It auto-reloads your app when its code is changed and you can also install it on Android phones to preview your app instantly. iOS is a bit more tricky cause of Apple's policies so it's not available on the App Store, but you can build it and install it yourself to your device.

      So that's my latest mobile stack. What tools do you use? Have you tried these ones?

      See more
      Jeyabalaji Subramanian

      At FundsCorner, when we set out to pick up the front-end tech stack (around Dec 2017), we drove our decision based on the following considerations:

      (1) We were clear that we will NOT have a hybrid app. We will start with Responsive Web & once there is traction, we will rollout our Android App. However, we wanted to ensure that the users have a consistent experience on both the Web & the App. So, the front-end framework must also have a material design component library which we can choose from.

      (2) Before joining FundsCorner as a CTO, I had already worked with Angular. I enjoyed working with Angular, but I felt that I must choose something that will provide us with the fastest time from Concept to Reality.

      (3) I am strong proponent of segregating HTML & JavaScript. I.e. I was not for writing or generating HTML through JavaScript. Because, this will mean that the Front-end developers I have to hire will always be very strong on JavaScript alongside HTML5 & CSS. I was looking for a Framework that was on JavaScript but not HEAVY on JavaScript.

      (3) The first iteration of the web app was to be done by myself. But I was clear that when someone takes up the mantle, they will be able to come up the curve fast.

      In the end, Vue.js and Vuetify satisfied all the above criteria with aplomb! When I did our first POC on Vue.js I could not believe that front-end development could be this fast. The documentation was par excellence and all the required essentials that come along with the Framework (viz. Routing, Store, Validations) etc. were available from the same community! It was also a breeze to integrate with other JavaScript libraries (such as Amazon Cognito).

      By picking Vuetify, we were able to provide a consistent UI experience between our Web App and Native App, besides making the UI development ultra blazing fast!

      In the end, we were able to rollout our Web App in record 6 weeks (that included the end to end Loan Origination flow, Loans management system & Customer engagement module). www.jeyabalaji.com

      See more
      JavaFX logo

      JavaFX

      235
      324
      9
      A Java library for building Rich Internet Applications
      235
      324
      + 1
      9
      PROS OF JAVAFX
      • 9
        Light
      CONS OF JAVAFX
      • 1
        Community support less than qt
      • 1
        Complicated

      related JavaFX posts

      PrimeFaces logo

      PrimeFaces

      88
      142
      3
      An open-source user interface component library
      88
      142
      + 1
      3
      PROS OF PRIMEFACES
      • 1
        JEE Integration
      • 1
        Support Contract available
      • 1
        Nice Components
      CONS OF PRIMEFACES
      • 1
        Some components have to be bought
      • 1
        JSF

      related PrimeFaces posts

      I need to modernize a Java web application that runs on JSF. I am used to building websites, so Bootstrap kinda feels like "home." But when it comes to applications, I feel Bootstrap is not the right way to go. Can someone explain to me what PrimeFaces is capable of in comparison with BS?

      See more
      React logo

      React

      127.3K
      105.2K
      3.9K
      A JavaScript library for building user interfaces
      127.3K
      105.2K
      + 1
      3.9K
      PROS OF REACT
      • 775
        Components
      • 658
        Virtual dom
      • 567
        Performance
      • 492
        Simplicity
      • 438
        Composable
      • 176
        Data flow
      • 162
        Declarative
      • 124
        Isn't an mvc framework
      • 114
        Reactive updates
      • 111
        Explicit app state
      • 40
        JSX
      • 24
        Learn once, write everywhere
      • 19
        Uni-directional data flow
      • 17
        Easy to Use
      • 14
        Works great with Flux Architecture
      • 10
        Great perfomance
      • 8
        Built by Facebook
      • 7
        Javascript
      • 5
        Speed
      • 5
        TypeScript support
      • 4
        Easy to start
      • 4
        Scalable
      • 4
        Awesome
      • 4
        Feels like the 90s
      • 4
        Hooks
      • 3
        Excellent Documentation
      • 3
        Scales super well
      • 3
        Functional
      • 3
        Obama
      • 3
        Fancy third party tools
      • 3
        Server side views
      • 3
        Props
      • 3
        Server Side Rendering
      • 3
        Cross-platform
      • 2
        Rich ecosystem
      • 2
        Start simple
      • 2
        Allows creating single page applications
      • 2
        Sdfsdfsdf
      • 2
        Beautiful and Neat Component Management
      • 2
        Very gentle learning curve
      • 2
        Has functional components
      • 2
        Simple
      • 2
        Closer to standard JavaScript and HTML than others
      • 2
        Super easy
      • 2
        Has arrow functions
      • 2
        Strong Community
      • 2
        Great migration pathway for older systems
      • 2
        SSR
      • 2
        Fast evolving
      • 2
        Simple, easy to reason about and makes you productive
      • 2
        Just the View of MVC
      • 1
        Sharable
      • 1
        Every decision architecture wise makes sense
      • 1
        Permissively-licensed
      • 1
        Split your UI into components with one true state
      • 1
        Fragments
      • 0
        Recharts
      CONS OF REACT
      • 36
        Requires discipline to keep architecture organized
      • 23
        No predefined way to structure your app
      • 22
        Need to be familiar with lots of third party packages
      • 9
        JSX
      • 7
        Not enterprise friendly
      • 5
        One-way binding only
      • 2
        State consistency with backend neglected
      • 2
        Bad Documentation
      • 1
        Paradigms change too fast

      related React posts

      Vaibhav Taunk
      Team Lead at Technovert · | 31 upvotes · 1.9M views

      I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

      See more
      Adebayo Akinlaja
      Engineering Manager at Andela · | 27 upvotes · 1.1M views

      I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen—since I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.

      A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.

      In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.

      If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.

      See more