[Here's mine](https://github.com/ScrimpyCat) I haven't had much public stuff happening on it recently since I've been busy with private projects. Though I have one other public project I need to put up on it just need to do a bit more work on it.

@kirby I wasn't really a fan of the language preview feature. Since their language detention wasn't so half the time it wasn't even that accurate.

Also I took the liberty of checking out your game repo and I have one suggestion as it's a possible bug at the moment. Your collision detection may not work sometimes depending on how fast you have the objects move. Since you're only checking for a collision at the destination, so if it moved so fast it's end destination is past an object it wouldn't actually detect the collision. If you're not going to have anything move that fast then this doesn't really matter but if you're here some possible solutions.

* A naive (but terribly slow) solution would be to increment the object the smallest distance it can travel and check for a collision then increment again, and keep repeating that until it either collides or has reached its destination.
* Create a physics system that updates at a faster interval than the game updates. This is what a lot of games will do, so it will take small steps each time and checking. And you just adjust the interval for performance and not movement bugs.
* Create a movement path. Create geometry representing the path the object takes for that movement and then check for collisions in that. This is the fastest approach but if you have complicated movement (beyond straight movements so like curved movements) it may get a little tricky depending in your experience.