Skip to content

Commit 721f40c

Browse files
authored
docs typo
1 parent 7f43c36 commit 721f40c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/history.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,7 @@ Less neat is the utter dearth of anyone writing WebAssembly in Rust without wasm
8888

8989
For the basic web UI stuff, I use [Svelte](https://svelte.dev/). I've never bothered to learn React, which I know is everyone's favorite, but Svelte fits my brain well. Never considered another toolkit. Right after I started, though, [Svelte 5 released](https://svelte.dev/blog/svelte-5-is-alive), which I decided to jump on because this was an early-stage project. That entailed some un-learning and learning, but on the whole I've been very happy with how easily Svelte lets me build stuff.
9090

91-
Then there was the question of game engine. Because I was trying to keep the non-WebAssembly parts of this strictly JavaScript (or TypeScript or what-have-you), that meant looking to web-native engines instead of something like Godot. This is not a space I knew very well, but research seemed to keep pointing back to [Phaser](https://phaser.io/), which I eventually settled on. Phaser is definitely one of the most popular web game frameworks, and it hits a nice sweet spot of functionality and relatively lightness. I don't love the documentation, though, and they recently moved everything to a new domain without properly redirecting old stuff, so even helpful articles and web searches have been made useless. I'm not pushing the engine too hard, but even just trying to do this simple stuff has been a little frustrating. The problem is almost certainly me, not Phaser, as lots of other people seem to be using it without problem. This may be a situation where I've gotten spoiled by using different tools meant for a different domain. (I also used to manage [my own 2D engine](https://github.com/angel2d/angel2d), so could just be over-opinionated.)
91+
Then there was the question of game engine. Because I was trying to keep the non-WebAssembly parts of this strictly JavaScript (or TypeScript or what-have-you), that meant looking to web-native engines instead of something like Godot. This is not a space I knew very well, but research seemed to keep pointing back to [Phaser](https://phaser.io/), which I eventually settled on. Phaser is definitely one of the most popular web game frameworks, and it hits a nice sweet spot of functionality and relative lightness. I don't love the documentation, though, and they recently moved everything to a new domain without properly redirecting old stuff, so even helpful articles and web searches have been made useless. I'm not pushing the engine too hard, but even just trying to do this simple stuff has been a little frustrating. The problem is almost certainly me, not Phaser, as lots of other people seem to be using it without problem. This may be a situation where I've gotten spoiled by using different tools meant for a different domain. (I also used to manage [my own 2D engine](https://github.com/angel2d/angel2d), so could just be over-opinionated.)
9292

9393

9494
## The Game!

0 commit comments

Comments
 (0)