Jawa vs Flax Engine
When comparing Jawa vs Flax Engine, the Slant community recommends Jawa for most people. In the question“What are the best game engines for point & click adventure games?” Jawa is ranked 15th while Flax Engine is ranked 54th.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Does not require coding
Pro Beginner-friendly
Pro Supports multiple platforms
Pro Browser engine
Pro Cosy
Pro Seems up-to-date
Pro Seems to be sky-rocketing in terms of popularity
Pro Resource sharing
The community can share resources with each other, as well as use default Jawa resources.
Pro Hosts wonderful video games
Pro Free
Can be used for free until you hit a rather high revenue cap, at which point you have to pay royalties.
Pro Powerful C# scripting
C# scripting is really well made, comparable to Unity, but without any of the legacy cruft.
Pro Multiplatform
Supports most platforms, including Windows, Linux, Android, Nintendo Switch, ...
Pro Modern rendering backend
Has a very modern, performant and beautiful rendering backend.
Pro C++ support
The entire core is written in C++ and it supports writing game code in C++. The interoperability between C# and C++ is also nothing to scoff at.
Pro Supports multiple IDEs
Works with any text editor and comes with proper support for Visual Studio, VSCode and Jetbrains Rider.
Pro Excellent documentation
The documentation is well written, up to date and accepts improvements from the community.
Pro Great and extensible editor
The editor is both powerful and simple. My favourite part is how easy it is to extend the editor with custom magic.
Pro Source code available
The entire source of the engine is available on Github, though not under an open source license.
Cons
Con Hosts just a few video games
Con Seems not fully translated
Jawa's main language is French.
Con Very small community
Con Hard to navigate
Con Looks out-dated
Con Buggy
Con New software
As is standard with new software, not all of the bugs have been ironed out yet.
Con Few plugins
Unlike more mature engines, there isn't a vibrant ecosystem of plugins yet.
Con Not open source
While the source code is available, it's not quite open source
Con Not latest C# version
It uses Mono and is still on some variant of C# 7.
Con No OpenGL support
It only supports modern APIs, namely Vulkan and DirectX. This means that it won't run on very old machines.