"it might stand to dethrone the venerable Flurry screensaver" - You are absolutely right. The first time I saw the screensaver, I was completely mesmerized and watched it for a few minutes before getting back to work.
Out of curiosity, why Rust? Not saying anything against it, just looking to understand your take on it.
1. It absolutely had to run in the browser.
2. I wanted the option of shipping native binaries later on, e.g. screensavers
This narrows the choice to something that can compile to WASM and has bindings for WebGL/OpenGL. Rust has substantial support for these technologies, there's an active graphics community, and, personally, it felt approachable for someone without experience with C/C++.
Also, I write Haskell/Elm for a living. I don't need much convincing to pick up another typed, memory-safe language.
Comments
"it might stand to dethrone the venerable Flurry screensaver" - You are absolutely right. The first time I saw the screensaver, I was completely mesmerized and watched it for a few minutes before getting back to work.
Out of curiosity, why Rust? Not saying anything against it, just looking to understand your take on it.
I had 2 requirements starting out:
1. It absolutely had to run in the browser. 2. I wanted the option of shipping native binaries later on, e.g. screensavers
This narrows the choice to something that can compile to WASM and has bindings for WebGL/OpenGL. Rust has substantial support for these technologies, there's an active graphics community, and, personally, it felt approachable for someone without experience with C/C++.
Also, I write Haskell/Elm for a living. I don't need much convincing to pick up another typed, memory-safe language.
Without a response from the parent, I'm guessing they wanted it to be in wasm, and Rust is one of the more popular languages for wasm development.