Alternatives to JavaFX logo

Alternatives to JavaFX

GWT, Vaadin, Qt, JSF, and Electron are the most popular alternatives and competitors to JavaFX.
236
322
+ 1
9

What is JavaFX and what are its top alternatives?

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.
JavaFX is a tool in the Cross-Platform Desktop Development category of a tech stack.

Top Alternatives to JavaFX

  • GWT
    GWT

    It is a development toolkit for building and optimizing complex browser-based applications. Its goal is to enable productive development of high-performance web applications without the developer having to be an expert in browser quirks, XMLHttpRequest, and JavaScript. ...

  • 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 ...

  • Qt
    Qt

    Qt, a leading cross-platform application and UI framework. With Qt, you can develop applications once and deploy to leading desktop, embedded & mobile targets. ...

  • JSF
    JSF

    It is used for building component-based user interfaces for web applications and was formalized as a standard through the Java Community ...

  • Electron
    Electron

    With Electron, creating a desktop application for your company or idea is easy. Initially developed for GitHub's Atom editor, Electron has since been used to create applications by companies like Microsoft, Facebook, Slack, and Docker. The Electron framework lets you write cross-platform desktop applications using JavaScript, HTML and CSS. It is based on io.js and Chromium and is used in the Atom editor. ...

  • Java
    Java

    Java is a programming language and computing platform first released by Sun Microsystems in 1995. There are lots of applications and websites that will not work unless you have Java installed, and more are created every day. Java is fast, secure, and reliable. From laptops to datacenters, game consoles to scientific supercomputers, cell phones to the Internet, Java is everywhere! ...

  • 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. ...

  • 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. ...

JavaFX alternatives & related posts

GWT logo

GWT

79
78
0
An open-source set of tools to create and maintain complex JavaScript front-end applications
79
78
+ 1
0
PROS OF GWT
    Be the first to leave a pro
    CONS OF GWT
      Be the first to leave a con

      related GWT posts

      Vaadin logo

      Vaadin

      157
      221
      34
      Components and tools for building web apps in Java
      157
      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

      Qt logo

      Qt

      367
      514
      119
      A leading cross-platform application and UI framework
      367
      514
      + 1
      119
      PROS OF QT
      • 15
        High Performance
      • 11
        Performance
      • 11
        Declarative, easy and flexible UI
      • 10
        Cross platform
      • 8
        Fast prototyping
      • 8
        Easiest integration with C++
      • 8
        Up to date framework
      • 6
        Safe 2D Renderer
      • 6
        Python
      • 5
        Great Community Support
      • 5
        Multiple license including Open Source and Commercial
      • 4
        HW Accelerated UI
      • 3
        True cross-platform framework with native code compile
      • 3
        JIT and QML Compiler
      • 3
        Game Engine like UI system
      • 2
        Reliable for industrial use
      • 2
        From high to low level coding
      • 2
        Been using it since the 90s - runs anywhere does it all
      • 2
        Easy Integrating to DX and OpenGL and Vulkan
      • 2
        No history of broken compatibility with a major version
      • 2
        Pure C++
      • 1
        Great mobile support with Felgo add-on
      CONS OF QT
      • 5
        Paid
      • 4
        C++ is not so productive
      • 1
        Lack of libraries
      • 1
        Not detailed documentation
      • 1
        Lack of community support

      related Qt posts

      JSF logo

      JSF

      118
      187
      4
      It is used for building component-based web interfaces
      118
      187
      + 1
      4
      PROS OF JSF
      • 2
        Rich and comprehensive Request Life-cycle
      • 1
        Very Mature UI framework
      • 1
        Server Side component
      CONS OF JSF
        Be the first to leave a con

        related JSF posts

        Hello guys! I would ask for your advice. Our situation is like that there will be a project to revamp workflows and introduce new services like mobile apps, machine learning, and some online services that would use cloud storage. We use JSF, JavaScript, Ajax, Spring, Oracle 12c running on Linux (VM) and providing online services to internal users and the public. But, we are not technically savvy enough to evaluate what tools should be introduced. Personally, I am evaluating whether to take this opportunity to change our practice/PM approach from Prince to Scrum/Agile (It seemed that DevOps is popular) ... Since we adopt ISO 27001 and ISO 20000, security is a crucial factor that we consider. Would you please help to recommend a list of tools and explain the reasons why you recommend them? Thanks in advance~!

        See more

        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
        Electron logo

        Electron

        8.8K
        7.9K
        137
        Build cross platform desktop apps with JavaScript, HTML, and CSS
        8.8K
        7.9K
        + 1
        137
        PROS OF ELECTRON
        • 66
          Easy to make rich cross platform desktop applications
        • 50
          Open source
        • 12
          Great looking apps such as Slack and Visual Studio Code
        • 6
          Because it's cross platform
        • 3
          Use Node.js in the Main Process
        CONS OF ELECTRON
        • 17
          Uses a lot of memory
        • 8
          User experience never as good as a native app
        • 4
          No proper documentation
        • 4
          Does not native
        • 1
          Each app needs to install a new chromium + nodejs
        • 1
          Wrong reference for dom inspection

        related Electron posts

        Slack's new desktop application was launched for macOS. It was built using Electron for a faster, frameless look with a host of background improvements for a superior Slack experience. Instead of adopting a complete-in-box approach taken by other apps, Slack prefers a hybrid approach where some of the assets are loaded as part of the app, while others are made available remotely. Slack's original desktop app was written using the MacGap v1 framework using WebView to host web content within the native app frame. But it was difficult to upgrade with new features only available to Apple's WKWebView and moving to this view called for a total application rewrite.

        Electron brings together Chromium's rendering engine with the Node.js runtime and module system. The new desktop app is now based on an ES6 + async/await React application is currently being moved gradually to TypeScript. Electron functions on Chromium's multi-process model, with each Slack team signed into a separate process and memory space. It also helps prevent remote content to directly access desktop features using a feature called WebView Element which creates a fresh Chromium renderer process and assigns rendering of content for its hosting renderer. Additional security can be ensured by preventing Node.js modules from leaking into the API surface and watching out for APIs with file paths. Communication between processes on Electron is carried out via electron-remote, a pared-down, zippy version of Electron's remote module, which makes implementing the web apps UI much easier.

        See more

        The Slack desktop app was originally written us the MacGap framework, which used Apple’s WebView to host web content inside of a native app frame. As this approach continued to present product limitations, Slack decided to migrate the desktop app to Electron. Electron is a platform that combines the rendering engine from Chromium and the Node.js runtime and module system. The desktop app is written as a modern ES6 + async/await React application.

        For the desktop app, Slack takes a hybrid approach, wherein some of the assets ship as part of the app, but most of their assets and code are loaded remotely.

        See more
        Java logo

        Java

        101.3K
        77.3K
        3.7K
        A concurrent, class-based, object-oriented, language specifically designed to have as few implementation dependencies as possible
        101.3K
        77.3K
        + 1
        3.7K
        PROS OF JAVA
        • 587
          Great libraries
        • 441
          Widely used
        • 400
          Excellent tooling
        • 387
          Huge amount of documentation available
        • 331
          Large pool of developers available
        • 203
          Open source
        • 200
          Excellent performance
        • 155
          Great development
        • 149
          Vast array of 3rd party libraries
        • 147
          Used for android
        • 60
          Compiled Language
        • 49
          Used for Web
        • 46
          Managed memory
        • 45
          High Performance
        • 44
          Native threads
        • 42
          Statically typed
        • 35
          Easy to read
        • 33
          Great Community
        • 29
          Reliable platform
        • 24
          JVM compatibility
        • 24
          Sturdy garbage collection
        • 21
          Cross Platform Enterprise Integration
        • 20
          Good amount of APIs
        • 20
          Universal platform
        • 18
          Great Support
        • 13
          Great ecosystem
        • 11
          Lots of boilerplate
        • 11
          Backward compatible
        • 10
          Everywhere
        • 9
          Excellent SDK - JDK
        • 7
          Static typing
        • 6
          Mature language thus stable systems
        • 6
          Better than Ruby
        • 6
          Long term language
        • 6
          Cross-platform
        • 6
          Portability
        • 6
          It's Java
        • 5
          Vast Collections Library
        • 5
          Clojure
        • 5
          Used for Android development
        • 4
          Most developers favorite
        • 4
          Old tech
        • 3
          Javadoc
        • 3
          Stable platform, which many new languages depend on
        • 3
          Best martial for design
        • 3
          Great Structure
        • 3
          History
        • 3
          Testable
        • 2
          Faster than python
        • 1
          Type Safe
        CONS OF JAVA
        • 32
          Verbosity
        • 27
          NullpointerException
        • 16
          Overcomplexity is praised in community culture
        • 14
          Nightmare to Write
        • 11
          Boiler plate code
        • 8
          Classpath hell prior to Java 9
        • 6
          No REPL
        • 4
          No property
        • 2
          Non-intuitive generic implementation
        • 2
          There is not optional parameter
        • 2
          Code are too long
        • 2
          Floating-point errors
        • 1
          Returning Wildcard Types
        • 1
          Java's too statically, stronglly, and strictly typed
        • 1
          Terrbible compared to Python/Batch Perormence

        related Java posts

        Conor Myhrvold
        Tech Brand Mgr, Office of CTO at Uber · | 40 upvotes · 4.9M views

        How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

        Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

        Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

        https://eng.uber.com/distributed-tracing/

        (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

        Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

        See more
        Kamil Kowalski
        Lead Architect at Fresha · | 28 upvotes · 1.4M views

        When you think about test automation, it’s crucial to make it everyone’s responsibility (not just QA Engineers'). We started with Selenium and Java, but with our platform revolving around Ruby, Elixir and JavaScript, QA Engineers were left alone to automate tests. Cypress was the answer, as we could switch to JS and simply involve more people from day one. There's a downside too, as it meant testing on Chrome only, but that was "good enough" for us + if really needed we can always cover some specific cases in a different way.

        See more
        React logo

        React

        128.4K
        104.7K
        3.8K
        A JavaScript library for building user interfaces
        128.4K
        104.7K
        + 1
        3.8K
        PROS OF REACT
        • 774
          Components
        • 657
          Virtual dom
        • 567
          Performance
        • 491
          Simplicity
        • 438
          Composable
        • 176
          Data flow
        • 162
          Declarative
        • 124
          Isn't an mvc framework
        • 114
          Reactive updates
        • 111
          Explicit app state
        • 39
          JSX
        • 23
          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
          Feels like the 90s
        • 4
          Hooks
        • 4
          Awesome
        • 4
          Scalable
        • 4
          Easy to start
        • 3
          Server Side Rendering
        • 3
          Fancy third party tools
        • 3
          Props
        • 3
          Obama
        • 3
          Server side views
        • 3
          Functional
        • 3
          Scales super well
        • 3
          Excellent Documentation
        • 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
        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