Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Threads are a bit of an issue. The entire web has been built on the premise that JavaScript is single-threaded. These days you can use web workers, but they have quite a few limitations. WASM threads have had a bumpy journey but should be available soon. I think eventually game engines will let you seamlessly compile for native and WASM with the only noticeable difference being performance. I know that macroquad and bevy are very close to something like this.
Threads are a bit of an issue. The entire web has been built on the premise that JavaScript is single-threaded. These days you can use web workers, but they have quite a few limitations. WASM threads have had a bumpy journey but should be available soon. I think eventually game engines will let you seamlessly compile for native and WASM with the only noticeable difference being performance. I know that macroquad and bevy are very close to something like this.
Because you have no idea what are you talking about but you need to express your manipulative opinion I will counter your "slowness" with real life benchmark https://www.techempower.com/benchmarks/#section=data-r20&hw=ph&test=json Look, JS on 4th place. With pure CPU task.
Related posts
- Limitations of wasm for a small board game?
- SDL2 vs Winit/Pixels/CPAL/etc. Is going "native" really worth it?
- Just a little question, can Bevy be used as a way for a beginner to learn Rust in general? also how much should I know before I start messing with Bevy?
- what GameEngine should i use to make games in rust?, is rust compile-time good enough for games?
- Why are most AAA games not written in Rust, but rather in C++?