urho3d VS phaser

Urho3D, an open source C++ game engine.

I believe Urho3d supports MacOS (see 'about' page on the legacy website).

Urho3D

If you're literally clueless your best bet is to first start learning with an existing clean-ish engine like Urho3D implementing whatever feature/screwing-around or start with a framework like nVidia's Donut that gets you your window and basic rendering in place.

I would recommend tracking through the gist of Urho3D's batch/batchqueue stuff as it's a reasonable setup that is very intelligible (if you speak C++), it's not the greatest thing on the planet but you should be able to roughly grok it in an afternoon. Doing draw batch-pumps greatly streamlines the final drawing code.

You could try Urho3D or its newer fork rbfx.

I use an engine called rbfx which is a fork of the Urho3D engine. A lot of it is just the fact that I've been using it for over a decade, so I am comfortable with it. I'm a programmer, not really comfortable with integrated editor engines such as Unity or Godot, and the easy C++ extensibility of the engine appeals to me. Plus it's decently powerful, and well supported on a lot of platforms (I build for Windows, WebGL, and very occasionally RPi for the most part) and is open source to satisfy that stubbornly libertarian side of my character.

You might be interested in Urho3D.

If you don't mind something experimental, there is a C# version of Urho3D that is in fairly active development. There is also a C#-scriptable branch of the Urho3D fork, rbfx, located here. Both of these projects are still pretty in-the-works, but are still pretty usable.

If you're targeting the browser first why not use a browser first library like PhaserJS [0]?. I don't see a reason to work around with WASM; HTML5 canvas might be everything that you need.

[0] https://phaser.io/

Gold : GitHub, Phaser Studio, Arcadia

Versatility: JavaScript is not limited to web browsers. It's used in a variety of environments, including mobile app development (using frameworks like React Native), game development (using libraries like Phaser), and even serverless computing (using platforms like AWS Lambda).

This reminds me of my first real dev job, 10y ago, making small facebook games with https://phaser.io it was actually kind of fun now that I think back.

Is it worth it? I think while attempting to create a game engine with the Canvas API and vanilla JavaScript. (I quickly ditched that idea and started using PhaserJS)

I didn't try to build anything with Phaser, but I evaluated it a bit when trying to pick a game engine for a 2D web game.

The tech didn't impress me that much, but it also seemed like the most mature 2D game engine available in JS.

Notably, Phaser 4 was announced ~four years ago and was an attempt to get the project written natively in TypeScript. It looks pretty dead in the water - https://github.com/phaserjs/phaser and having a "best effort" TypeScript experience layered onto Phaser 3 didn't excite me.

Additionally, with browsers gaining support for WebGPU, I expect any game engine worth their snuff to begin rapidly adopting support for WebGPU. As best I can tell, any hope of Phaser supporting WebGPU is lumped into Phaser 4, so... not much to say there.

Overall, it was a little tough for me to tell if I was being overly critical and viewing a mature product as a ghost town, but that's the impression I took away from it.

As far as I can tell, BabylonJS is king in town for a TypeScript game engine, but its focus is 3D experiences. I didn't find an especially compelling 2D game engine. I ended up making a prototype using React + PixiJS + React-Pixi, but that was hardly an engine and had significant performance issues.

Now I am building in Rust with Bevy. It's slow going, creating UI elements sucks right now, but the underlying tech is super solid and I feel good about what I write and what I learn even if I'm dismayed at the pace in which I am creating.