When comparing pygame vs Phaser.io, the Slant community recommends Phaser.io for most people. In the question“What are the best 2D game engines?” Phaser.io is ranked 10th while pygame is ranked 19th. The most important reason people chose Phaser.io is:
Ranked in these QuestionsQuestion Ranking
Pro Easy Python syntax
Pygame uses Python as its scripting language. Python is widely considered one of the easiest languages to grasp even for beginners.
Pro Very easy to understand
The API is very straightforward.
Pro Good canvas system
Pygame has a drawing system that allows the user to create and draw on an unlimited number of canvases.
Pro Very fast to develop with
Pro Good tutorials, courses and books
There are plenty of great learning resources available for Phaser.io.
Pro Super-simple loading of assets
Pro Great community resources
Pro Animating is easy
Pro Excellent tools for sprites
Pro Built-in Arcade Particle system
Pro Easy to learn
Pro Support for Arcade Physics, Ninja Physics and p2.js
Pro No install required
All you need to do is attach Phaser script to a HTML page even without installing any extensions.
Pro Very active development
This is one of the most developed frameworks right now.
Pro WebGL and Canvas rendering modes
You can choose WebGL or classic HTML canvas element for game rendering.
Pro Easy to learn
Most task are done just using 2 or 3 lines of codes...
Pro Has separate versions maintained by developer and the community
The creator of phaser(photonstorm) has given the older(Phaser 2.0) source code to the community for their own maintenance, and has made Phaser 3.0 with a different style and approach, trying to make it easier for beginners to learn.
Pro Easy to understand if you have used flash
Phaser provides a similar approach as to that of Flash games, where you can load assets and place them on a stage, and even improves upon the shortcomings of actionscript. It is very easy to shift from flash to HTML5 development because of this approach.
Con Very basic
Pretty much just a wrapper for SDL.
Con Messy documentation
The docs are messy, and some basic functions are infuriating to work out. There's even some places in the documentation where it's clearly wrong about how a method is called/what the arguments really do.
Con Deathly slow
Con Nonexistent community
No good forums, wiki, or other ways to reach other Pygame developers.
Con Hasn't been updated in years
Hasn't been updated in years.
Pygame uses a really old version of SDL and is missing some of the features developed for SDL2.
Con Pygame is a language, not a game engine
Physics, AI, networking, and input are not supported.
Con Poor performance
As long as your map is not larger than 600*400px, everything is fine.