Raylib-CsLo VS phaser

I wonder if it would be worth a try to use Raylib-CsLo. That would for sure confirm a binding issue.

Long time [Raylib_CsLo](https://github.com/NotNotTech/Raylib-CsLo) user, first time C user.

I'm under the impression that Unity builds have a good deal of overhead. Plus, in many cases, something like raygui (C# bindings) will actually be quicker to develop with. Nothing wrong with Unity, though. The best tool is the one you know how to use, in my opinion.

I'm a big fan of Raylib-cslo.

Regardless, the C# binding I'm using is Raylib-CsLo which autogenerates the binding around the original C library, at least as far as I understand it. Maybe you could reach out to the developer (via Discord/Github) and ask him how it's done.

I wrote a C# binding for Raylib, which I am going to try building up into a kid-friendly framework: https://github.com/NotNotTech/Raylib-CsLo

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.