Alternatives to GWT logo

Alternatives to GWT

JavaFX, Vaadin, Angular 2, Spring, and Dart are the most popular alternatives and competitors to GWT.
66
71
+ 1
0

What is GWT and what are its top alternatives?

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.
GWT is a tool in the Javascript UI Libraries category of a tech stack.

Top Alternatives to GWT

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

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

  • Angular 2

    Angular 2

    It is a TypeScript-based open-source web application framework. It is a development platform for building mobile and desktop web applications. ...

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

  • Dart

    Dart

    Dart is a cohesive, scalable platform for building apps that run on the web (where you can use Polymer) or on servers (such as with Google Cloud Platform). Use the Dart language, libraries, and tools to write anything from simple scripts to full-featured apps. ...

  • 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

    JSF

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

  • Blazor

    Blazor

    Blazor is a .NET web framework that runs in any browser. You author Blazor apps using C#/Razor and HTML. ...

GWT alternatives & related posts

JavaFX logo

JavaFX

224
291
5
A Java library for building Rich Internet Applications
224
291
+ 1
5
PROS OF JAVAFX
  • 5
    Light
CONS OF JAVAFX
  • 1
    Community support less than qt
  • 1
    Complicated

related JavaFX posts

Vaadin logo

Vaadin

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

related Vaadin posts

Angular 2 logo

Angular 2

4.7K
3.7K
419
A platform for building mobile and desktop web applications
4.7K
3.7K
+ 1
419
PROS OF ANGULAR 2
  • 96
    It's a powerful framework
  • 48
    Straight-forward architecture
  • 41
    TypeScript
  • 40
    Great UI and Business Logic separation
  • 38
    Powerful, maintainable, fast
  • 36
    Amazing CLI
  • 30
    Great mvc
  • 23
    Powerfull Dependency Injection
  • 18
    Easy to build
  • 13
    Opinionated, batteries-included approach
  • 11
    All in one Framework
  • 8
    Schematics
  • 7
    Solid Standard Setup.
  • 6
    Performance
  • 6
    Structured
  • 3
    Complex
  • 3
    Only for single page applications
  • 2
    Builders
  • 1
    RxJS
  • 1
    Ng upgrade
  • 0
    React
CONS OF ANGULAR 2
  • 9
    Overcomplicated
  • 9
    Large overhead in file size and initialization time
  • 2
    Ugly code
  • 2
    Cringe
  • 2
    CLI not open to other test and linting tools

related Angular 2 posts

When Redash was created 5 years ago we chose AngularJS as our frontend framework, but as AngularJS was replaced by Angular 2 we had to make a new choice. We decided that we won't migrate to Angular, but to either React or Vue.js. Eventually we decided to migrate to React for the following reasons:

  1. Many in our community are already using React internally and will be able to contribute.
  2. Using react2angular we can do the migration gradually over time instead of having to invest in a big rewrite while halting feature development.

So far the gradual strategy pays off and in the last 3 major releases we already shipped React code in the Angular.js application.

See more
Max Musing
Founder & CEO at BaseDash · | 10 upvotes · 278K views

From my experience of the early startup world, a majority of companies these days use Node.js. Python and Go are the next biggest languages, but significantly smaller than Node.

However, if you're having trouble with the front end aspect of Django, using Node probably won't make that easier for you. You'll have a lot more options between front end frameworks (React, Vue.js, Angular 2) , but they'll definitely take more time to learn than Django's templating system.

Think about whether you want to focus on front end or back end for now, and make a decision from there.

See more
Spring logo

Spring

3.3K
3.9K
1K
Provides a comprehensive programming and configuration model for modern Java-based enterprise applications
3.3K
3.9K
+ 1
1K
PROS OF SPRING
  • 220
    Java
  • 154
    Open source
  • 132
    Great community
  • 119
    Very powerful
  • 111
    Enterprise
  • 62
    Lot of great subprojects
  • 58
    Easy setup
  • 44
    Convention , configuration, done
  • 37
    Standard
  • 29
    Love the logic
  • 11
    Good documentation
  • 10
    Dependency injection
  • 9
    Stability
  • 6
    MVC
  • 6
    Easy
  • 3
    Strong typing
  • 3
    Makes the hard stuff fun & the easy stuff automatic
  • 2
    Code maintenance
  • 2
    Best practices
  • 2
    Maven
  • 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
  • 1
    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
Dart logo

Dart

2.4K
2.7K
397
A new web programming language with libraries, a virtual machine, and tools
2.4K
2.7K
+ 1
397
PROS OF DART
  • 52
    Backed by Google
  • 45
    Flutter
  • 37
    Twice the speed of Javascript
  • 32
    Great tools
  • 28
    Scalable
  • 24
    Open source
  • 22
    Can be used on Frontend
  • 22
    Made for the future
  • 21
    Polymer Dart
  • 21
    Angular Dart
  • 16
    Cross platform
  • 14
    Like Java
  • 11
    Runs on Google Cloud Platform
  • 11
    Easy to learn
  • 11
    Dartanalyzer
  • 8
    Amazing concurrency primitives
  • 7
    Easy to Understand
  • 7
    Is to JS what C is to ASM
  • 4
    Flutter works with darts
  • 2
    Can run Dart in AWS Lambda
  • 2
    R
CONS OF DART
  • 3
    Lack of ORM
  • 3
    Locked in - JS or TS interop is very hard to accomplish
  • 0
    A

related Dart posts

Gustavo Muñoz
Senior Software Engineer at JOOR · | 8 upvotes · 381K views

In my modest opinion, Flutter is the future of mobile development. The framework is as important to mobile as React is to the web. And seeing that React Native does not finish taking off, I am focusing all my efforts on learning Flutter and Dart. The ecosystem is amazing. The community is crazy about Flutter. There are enough resources to learn and enjoy the framework, and the tools developed to work with it are amazing. Android Studio or Visual Studio Code has incredible plugins and Dart is a pretty straight forward and easy-to-learn language, even more, if you came from JavaScript. I admit it. I'm in love with Flutter. When you are not a designer, having a framework focused on design an pretty things is a must. And counting with tools like #flare for animations makes everything easier. It is so amazing that I wish I had a big mobile project right now at work just to use Flutter.

See more

I am currently working on a long term mobile app project. Current stack: Frontend: Dart/Flutter Backend: Go, AWS Resources (AWS Lambda, Amazon DynamoDB, etc.) Since there are only two developers and we have limited time and resources, we are looking for a BAAS like Firebase or AWS Amplify to handle auth and push notifications for now. We are prioritizing developing speed so we can iterate quickly. The only problem is that AWS amplify support for flutter is in developer preview and has limited capabilities (We have tested it out in our app). Firebase is the more mature option. It has great support for flutter and has more than we need for auth, notifications, etc. My question is that, if we choose firebase, we would be stuck with using two different cloud providers. Is this bad, or is this even a problem? I am willing to change anything on the backend architecture wise, so any suggestions would be greatly appreciated as I am somewhat unfamiliar with Google Cloud Platform. Thank you.

See more
React logo

React

113.9K
91.4K
3.8K
A JavaScript library for building user interfaces
113.9K
91.4K
+ 1
3.8K
PROS OF REACT
  • 760
    Components
  • 652
    Virtual dom
  • 563
    Performance
  • 486
    Simplicity
  • 436
    Composable
  • 175
    Data flow
  • 159
    Declarative
  • 124
    Isn't an mvc framework
  • 113
    Reactive updates
  • 111
    Explicit app state
  • 32
    JSX
  • 23
    Learn once, write everywhere
  • 19
    Uni-directional data flow
  • 16
    Easy to Use
  • 14
    Works great with Flux Architecture
  • 10
    Great perfomance
  • 8
    Built by Facebook
  • 7
    Javascript
  • 5
    TypeScript support
  • 5
    Speed
  • 4
    Feels like the 90s
  • 4
    Scalable
  • 4
    Easy to start
  • 4
    Awesome
  • 3
    Fancy third party tools
  • 3
    Hooks
  • 3
    Functional
  • 3
    Server side views
  • 3
    Props
  • 2
    Rich ecosystem
  • 2
    Obama
  • 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
    Excellent Documentation
  • 2
    Scales super well
  • 2
    Just the View of MVC
  • 2
    Server Side Rendering
  • 2
    Cross-platform
  • 1
    Fragments
  • 1
    Start simple
  • 1
    Every decision architecture wise makes sense
  • 1
    Permissively-licensed
  • 1
    Beautiful and Neat Component Management
  • 1
    Sdfsdfsdf
  • 1
    Allows creating single page applications
  • 1
    Split your UI into components with one true state
  • 1
    Sharable
CONS OF REACT
  • 35
    Requires discipline to keep architecture organized
  • 23
    No predefined way to structure your app
  • 21
    Need to be familiar with lots of third party packages
  • 8
    JSX
  • 7
    Not enterprise friendly
  • 4
    One-way binding only
  • 2
    State consistency with backend neglected
  • 2
    Bad Documentation

related React posts

Vaibhav Taunk
Team Lead at Technovert · | 31 upvotes · 1.6M 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 · | 26 upvotes · 790K 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
JSF logo

JSF

110
160
4
It is used for building component-based web interfaces
110
160
+ 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
    Blazor logo

    Blazor

    283
    423
    150
    An experimental web UI framework using C#/Razor and HTML, running in the browser via WebAssembly
    283
    423
    + 1
    150
    PROS OF BLAZOR
    • 27
      Uses C#
    • 19
      No need to learn separate language or technology
    • 17
      Supports making a single page application
    • 17
      Uses .NET standard library
    • 16
      Tight integration with .NET project
    • 12
      No need to compile, bundle and deploy separately
    • 10
      Very little JavaScript required
    • 8
      Shared classes between client and server
    • 5
      Components
    • 5
      Third party state management i.e. Blazor-State
    • 5
      App state can be managed singleton objects
    • 4
      Very easy JavaScript interop if required
    • 3
      Has Server AND Client hosting models
    • 2
      Cross Platform
    CONS OF BLAZOR
    • 3
      Initial load time
    • 2
      Hard to inject javascript

    related Blazor posts