jMonkeyEngine VS gopherjs

At the time of the check, the latest revision was the e584cb1 commit. We checked it using the static analyzer.

> Unfortunately, this is yet another open source game engine with too small a user base.

I wonder why some engines are seemingly destined for success and others... aren't.

Godot got really big, despite a somewhat similar feature set: https://godotengine.org/ (really nice 2D support, 3D rendering was worse until version 4, GDScript has both a nice iteration speed but also has gotten some criticism, while C# was a second class citizen in the earlier iterations)

Stride is really nice and seemed like it should have been the Unity replacement that people would look at, if it had gotten more attention and a community would have formed around it, like Godot's.

There's also NeoAxis which is way more Windows centric, but still seems to be getting updates and is comparatively easy to use, yet similarly never got popular: https://www.neoaxis.com/

Weirder yet, Java doesn't really have that many game engines out there, at least the likes of Unity/NeoAxis/Stride that have nice editors, despite the language being pretty nice. The closest I can think of is jMonkeyEngine which I donated some money in the past to, which is pretty usable but similarly niche: https://jmonkeyengine.org/

I occasionally watch videos on the Gamefromscratch YouTube channel (https://www.youtube.com/@gamefromscratch/videos) and it surprises me that there are so many engines out there, but very few actually are in the public eye. If you don't go out of your way to look for other options, you will most likely only have heard of Unity and Unreal (or maybe also Godot in recent years). I wonder why that is.

There more `bare-metal` engines like https://jmonkeyengine.org/ (well it is not C++, it is Java based)...

jMonkeyEngine (Java, Open source): https://jmonkeyengine.org/

This project develops a cross-platform Subspace client and server written in Java. It was developed from scratch on the idea of extensibility and modularity. The server is based on modules/frameworks highly optimized for scaled, networked, grid-based, infinite world physics. The client is based on the JMonkeyEngine, a minimalistic modern developer friendly, open source, game engine

> Godot is one of those pinnacle FOSS projects that just totally impresses me, especially given the state its in now, with 4.0.

It is definitely one of the success stories, at least so far.

For example, there are projects like jMonkeyEngine (a game engine in Java, on top of LWJGL) that don't get as much attention and their movement forwards is way slower: https://jmonkeyengine.org/

There's also Stride 3D, which is a bit closer to Unity I'd say, which is still a really nice project, but is also limited in how much development can be done: https://www.stride3d.net/

Regardless, I wish all of those projects success and would still be glad if Godot could be one of the champions of open source game engines, perhaps as a viable and easy to use alternative to something like Unity for those who want that sort of thing, even in the professional development space eventually!

It is, or at least was, efficient. Java has a great game engine called https://jmonkeyengine.org/ that at the time could compete with Unity, not sure the status now. And LWJGL, the lower layer for ooengl, was quite nice to use and it is efficient to go that low level if you plan to do a game that does not fit the stereotypes in such game engines, as you will find yourself fighting the engine more than the actual game.

This seems interesting https://jmonkeyengine.org , how would I get started?

IDE: use whatever make you productive. I personally use vscode. VCS: git, as golang communities use github heavily as base for many libraries. AFAIK Linter: use staticcheck for linting as it looks like mostly used linting tool in go, supported by many also. In Vscode it will be recommended once you install go plugin. Libraries/Framework: actually the standard libraries already included many things you need, decent enough for your day-to-day development cycles(e.g. `net/http`). But here are things for extra: - Struct fields validator: validator - Http server lib: chi router , httprouter , fasthttp (for non standard http implementations, but fast) - Web Framework: echo , gin , fiber , beego , etc - Http client lib: most already covered by stdlib(net/http), so you rarely need extra lib for this, but if you really need some are: resty - CLI: cobra - Config: godotenv , viper - DB Drivers: sqlx , postgre , sqlite , mysql - nosql: redis , mongodb , elasticsearch - ORM: gorm , entgo , sqlc(codegen) - JS Transpiler: gopherjs - GUI: fyne - grpc: grpc - logging: zerolog - test: testify , gomock , dockertest - and many others you can find here

Release notes have all the details. For now it is just compatibility with the 1.18 standard library, but generics support is planned.

Why not use https://github.com/gopherjs/gopherjs with jMonkeyEngine as-is?

When I wrote my first project in this year, I don't even planed to used blazor. But my childlike curiosity directed me on that path. I wanted to know, haw hard will be port game from desktop to web browser in .net. And I found out is not that hard. But I have experience with similar tools before. I used gopherjs and emscripten. Thanks to that I know what must to do, to communicate c# with javasrcipt. I made working blazor port pretty fast. Not only server side but webassembly to. Of curs create port for different platform always generate some problems. Most weird problem I have in blazor is how floating point number behave. I received in some cases NaN values. This problem I resolve adding value like 0.0001 in calculation.

If you're already building the backend in go and you don't like the prospect of coding in JavaScript it might be worth trying out https://github.com/gopherjs/gopherjs

Maybe this is were https://github.com/gopherjs/gopherjs will truly shine? Has anyone ever seen Go used for this?

You can also write JS in Go with GopherJS, but if you don't fully understand the underlying JS webdev ecosystem, adding this extra layer of complexity is probably a really bad idea, at least at first.