game engine comparison 2022

 

1. haxeflixel
1. (+) code only
2. (+) strong typing 
3. (+) built-in debugger
   
4. (0) async programming: FlxSignal/add/dispatch
5. (0) so so ui components 
1. haxeui: crash on neko target
2. flixel-ui: ok for xml, meh for code only(no proper scaling)
3. FlxUISpriteButton + loadGraphicSlice9
6. (-) unpopular
7. (-) demo could not load hexagonal tmx  
8. (-) buggy? unable to resize text on FlxButton
9. (-) incomplete documents 
10. (-) no anchor for sprite support
    
2. heaps.io
1. (-) no default UI library?
   
3. godot
1. (+) popular
2. (+) rich ui components 
3. (+) easy to include assets
4. (+) plugin load hexagonal tmx
   
5. (0) async programming : signal/connect/emit_signal
   
6. (-) weak typing
7. (-) editor needed 
4.  ebiten
1. (+) strong typing
2. (+) go-tiled load hexagonal tmx(?)
3. (+) boot faster than ceramic(2.5~3x?)
   
4. (0) async programming : go routine
5. (-) less ui components (text, button)
6. (-) need to encode assets(?)
5. love2d + moonscript
1. (+) fast iteration
2. (-) slow
3. (-) script only
   
4. (-) no default UI library
   
6. cocos2d-x
1. (-) hard to build
2. (-) long test cycle
3. (-) big commit size
7. sfml
1. (-) mobile build?
8. ceramic
1. (+) code only
2. (+) strong typing 
3. (+) anchor for sprite support
4. (?) async programming: (Timer/delay/interval)
5. (=) lighter than haxeflixel but less component 
1. less decoration for text
2. async rendertexture
   
6. (-) unpopular
7. (-) could not load hexagonal tmx  
8. (-) no built-in functional UI system(though there're UI components)
   
9. (-) incomplete documents
10. (-) slower to boot than ebiten
    
9.