GodotSteam VS emscripten

Here I'm already trying to use dll and template from windows prebuild win64-g353-s158-gs3221.zip from https://github.com/CoaguCo-Industries/GodotSteam/releases, same results

get libgodotsteam.so + libsteam_api.so from here: https://github.com/CoaguCo-Industries/GodotSteam/releases/tag/g352-s157-gdn363

That at least gives me hope that the ecosystem will adapt quickly. And I noticed GodotSteam for instance delivered a 4.0 compatible release today already: https://github.com/Gramps/GodotSteam/releases

Wild to me this is being released on the iphone before being mac compatible on steam considering it already runs flawlessly on mac when you import the files from a windows pc and paste two files into the install folder and run it. I just did this and it's perfect, it would literally take him minutes of his time to make this available to OSX users.

You need this Godot build first, it is practically Godot for building games with Steam.

That said, WebAssembly’s ecosystem is still fragmented. Tools like Emscripten (C/C++), wasm-bindgen (Rust), and JSGo (Go) serve different languages, but this complicates the standardization of interactions with web APIs, limiting broader WASM integration with web development.

Browsers limit the ability for these platforms to use raw sockets, there simply is no API for it. The best that can be done /today/ is to use WebSockets, which are not the same thing any can't be used for HTTP requests without the server expecting a WebSocket connection:

https://github.com/emscripten-core/emscripten/issues/5196#is...

Only half true. Emscripten implements the SDL 1.2 (and also SDL_mixer 1.2) API in Javascript here: https://github.com/emscripten-core/emscripten/blob/main/src/.... On the other hand SDL 2 (and SDL_mixer 2) are proper ports (which you linked to).

So there's quite a size penalty to using SDL 2 rather than SDL 1.2.

Playing with low-level stuff is fun, but I won't use it anywhere in productionable code. Well, at least without considerable experience and understanding of the Emscripten code base.

Thank you for your comment!

WASM gave Figma a lot of speed by default for a lot of perf-sensitive code like rendering, layouts, applying styles and materializing component instances, our GUI code is mostly React and CSS.

WASM engine performance has not been a problem for us, instead we are constantly looking forward improvements in the devex department: debugging, profiling and modularization.

One of the largest challenges of the platform we face today is the heap size limit. While Chrome supports up to 4GB today, that's not yet the case for all browsers. And even with that, we are still discovering bugs in the toolchain (see this recent issue filed by one of our engineers) https://github.com/emscripten-core/emscripten/issues/20137

The challenge of the perf-testing at scale in our company is helping developers to detect perf regressions when they don't expect them - accidental algorithmic errors, misused caches, over-rendering React components, dangerously inefficient CSS directives, etc.

https://github.com/emscripten-forge/recipes/tree/main/recipe...

Re: emscripten fs implementations: https://github.com/emscripten-core/emscripten/issues/15041#i... https://github.com/jupyterlite/jupyterlite/issues/315

Moving onto the project, let’s first install Emscripten from their git repository. Emscripten will compile C into Wasm code. An important note is that I will be using Mac OS for this project. If you want to follow along using Windows, use this link. To Begin, open your terminal and clone down Emscripten with:

I got pointed to this one here: https://github.com/emscripten-core/emscripten/issues/15487