Normally I'd wait until ggez 0.6.0 is released for good to create such a PR, but for some people text performance on ggez 0.5.1 is really awful, which was fixed now, luckily. And now that I found this pretty little library I don't want it to appear sluggish because of problems in ggez.
For example:
I get between 11 and 45 FPS running the example in release mode using ggez 0.5.1
I get around 1400 FPS using ggez 0.6.1-rc1 in release mode
Also, since ggez will (hopefully) get to 0.6.0 in the not too distant future and not much of the new API should change until then, updating the example to use the new API just makes sense, I guess.
Not a massive improvement for me (I'm on an RX 590) but I see no reason not to merge it. Since it's just an example relying on a release candidate is fine.
Normally I'd wait until ggez 0.6.0 is released for good to create such a PR, but for some people text performance on ggez 0.5.1 is really awful, which was fixed now, luckily. And now that I found this pretty little library I don't want it to appear sluggish because of problems in ggez.
For example:
Also, since ggez will (hopefully) get to 0.6.0 in the not too distant future and not much of the new API should change until then, updating the example to use the new API just makes sense, I guess.