Socket.io VS Phaser

The purpose of Asynction is to empower a specification first approach when developing SocketIO APIs in Python. It guarantees that your API will work in accordance with its documentation.

socket.io is probably a good first step into this as it's very straightforward to use and will introduce you to principles that you can use for more complicated things going forward 💪

However, being AWS, WebSocket implementation is the bare minimum, no retry, no resume, not compatible with socket.io JS framework you must use raw WebSocket API in JS and building own wrapper would take several weeks so I've looked at alternatives like Ably.

Basically I am working on the project where we need to built the chat application for the client in MERN stack. I am familiar with the MERN stack, and worked on multiple projects and React.js in general is the technology that I am working on for almost 2 years now. I now about Socket.io and watched a few courses on "how to build the chat app using socket.io and React.js".

Check out socket.io. Depending on where you are in your journey, it might be a little tricky, or it might be not too bad.

The forked process can send messages back to the parent process so you will still have access to the array and the socket.io instance. For example, API request finishes in the forked process then it sends a message to its parent and the parent handles the message accordingly.

I wanted to make a connection on the socket.io so I used python-socket.io in the backend (FastAPI) and socket.io-client for the frontend(React.js) but I have been getting connection failed error (403 Forbidden).

i dont know how to fix it, i set the port by: const io = require('socket.io')(3000), any ideas? i think i might have to set the port a different way in order to work on heroku

And I do recommend using socket.io over raw websockets handling. Way more handy frontend and backend side.

My little bro is 13, I taught him to go program in phaser.io to make 2d games, as well as with unity. His goal was to publish something (doesn't matter what) and have some ad revenue in it. Use alot of templates was my advice :D

Start with a single player web game first then. Mutliplayer is not something that's suitable for a beginner. Phaser is a good start for web games.

Phaser

You could do it in Javascript with phaser.io

If you are looking to make a game it might be good to start with phaser.io.

How do you feel about JavaScript? http://phaser.io/

If your looking for a game engine I would check out Phaser (https://phaser.io/)

You might want to look at phaser.io depending on what you are building

Create a game that, after some condition is met, yields an NFT transfer to the player. Since this needs to run in the browser, I was going to use phaser.js, but then I realized that's a terrible idea (see step 4) and will have to use unity, or maybe I'll learn something new and try Defold?

You're working at an indie game company. A small top-down shooter that you've written in JavaScript with Phaser. Your bass has asked you to implement a user score.