gamedev_libraries VS tracy

If you don't like my suggestions for libraries, or want to explore more complex topics like serialization and scripting, check out this master list of gamedev libraries: https://github.com/raizam/gamedev_libraries

You can also try use C++, which I think you commented on here as what you prefer. Similarly, you should usually start with knowing how to code in the language first, and then find libraries that you might need to add more ✨ pizzaz ✨ sa game. Can try to see this list or this github repo hahaha i'm not a game developer, but i just have these saved randomly. hope it helps!

Yes, but the bulk of the effort isn't going into engines or ports. And it's certainly not going into proprietary equivalents of libraries like SDL2 or Dear ImGui.

Tools make it seem like you press buttons and things happen, You will find more if you look for libraries. https://github.com/raizam/gamedev_libraries.

If you really don't want to work with HTML & CSS, you'll probably need to extend Node.js with native C++ modules to architect your engine.

i don't really think there is _anything_ that comes even close to tracy https://github.com/wolfpld/tracy.

on top of this, given google's penchant for dumping projects aka abandonware, this would be an easy pass.

The RemedyBG debugger (https://remedybg.handmade.network/) and the Tracy profiler (https://github.com/wolfpld/tracy) both use Dear ImGui and so far I've only read high praise from people who used those tools compared to the 'established' alternatives.

For tools like this, programmers are also just "normal users", and from the developer side, I'm sure they evaluated various alternatives with all their pros and cons before settling for Dear ImGui.

Not the person you asked, but generally you might want to look at "frame-based" profilers. These are typically used in video games, but the concept is general, and can apply to other applications. The "frame" could also be something like a request or transaction being processed. I like Tracy[1], myself.

Another latency metric that you'll see, often w/respect to web apps and microservices is "P99" and similar. This is the amount of time in which 99% of requests get their response. For a higher percentile, you get a better idea of worst-case performance.

[1] https://github.com/wolfpld/tracy

I've not actually used Superluminal, but I use Tracy for similar reasons. It's free though (and, importantly, open source).

For profiling, you can check tracy.

You could try Tracy

There is no such thing as overengineering in fun projects, so I've also adopted Tracy as profiling solution. Works quite nice and gonna save me plenty of times in the future debugging performance spikes on badly optimized math heavy operations.

I know about tools such as tracing, jaeger or tracy. While having a complete tracing could be a potential solution, these tools don't work with no_std.