phaser VS React

https://phaser.io/tutorials/making-your-first-phaser-3-game/...

Gold : GitHub, Phaser Studio, OP Games, Playhop

This is super cool & I'm impressed that it's working with WebGL.

From reading the code & seeing the examples in the sandbox, it looks like the sprite layer is defined one time (initialization) with specific sprite & animation properties that are exposed to JS via the SpriteGPULayer config https://github.com/phaserjs/phaser/blob/v4.0.0-beta.5/src/ga... , then that class passes the info over to the vertex shader which has ifdefs to determine which animation, other features are enabled for a given SpriteGPULayer - https://github.com/phaserjs/phaser/blob/v4.0.0-beta.5/src/re...

This way you don't end up having to do any updates per frame on the CPU and it remains one draw call for the entire layer right?

Are there other use cases besides from large scale sprite/animated backgrounds that you've thought of?

I've started working on a simple interactive version of my portfolio using Phaser.js.

This is first time i used Phaser for making a game but it's a very nice and easy HTML5 framework and i follow tutorial to use phaser and after few of them, i tried to add few things and make the gameplay how i would enjoy, so i learn about spritesheets and audios and then how many states we have to keep in mind while building a game, like preload(), create() and update() and how to manage these before adding anything or changing in the game. 👾

Phaser

https://phaser.io/. It’s more of a game framework in JavaScript with built in libraries for collision. The getting started tutorial is decent/short and gives a good idea of what is going on.

Phasor which uses TypeScript or JavaScript

Official React Documentation: react.dev MDN Javascript Documentation: developer.mozilla.org/JavaScript

Early in my career, I struggled to understand how React’s state updates actually worked. Docs gave me the basics, but edge cases around batching were confusing. One weekend, I pulled up the React source code on GitHub and traced how state changes bubbled through the scheduler. Suddenly, the “weird bugs” I hit at work made sense because I wasn’t guessing anymore, I’d seen the engine.

3. Next.js and React (Frontend framework)

My primary passion is backend development, but I wanted to build a user-friendly frontend to complete this project. Given my experience with React, Next.js was the obvious choice due to its excellent documentation and ease of use.

Check out the React 19 Upgrade Guide for more details. Have fun coding, and share in the comments what you’re building with React 19! 🎉

React Official Documentation — Start here for official guides and tutorials

At IVAO, we partially follow micro-services best practices. This means each business group (e.g., Flight tracking, Flight planning, Air Traffic controlling, Training) has its own NestJS API and ReactJS frontend. But we took a shortcut on the DB side, as we have quite some references across systems, especially for user IDs, airports, etc... We decided to have a single MariaDB instance while having a dedicated logical database for each API, so we still have a separation of concerns but we can guarantee data integrity with foreign keys across those databases.

React.js (fast, large ecosystem)

Tools: V0 by Vercel, shadcn/ui, React, Tailwind CSS V0 turns natural language prompts into ready-to-use React + Tailwind UI code. Ask for “a responsive SaaS dashboard with a dark theme and collapsible sidebar” and you get production-ready code instantly, accessible, tweakable, and not locked into rigid templates.