Kha

At its core the beauty of Flash was the extremely tight interplay between vector graphics in nested timelines, and the the programming environment. Many people compare Flash to Unity, but I really don't find the two all that comparable. You don't create your assets in Unity, and by the time those assets get into Unity you have lost most potential for dynamic behaviour. Flash's tight integration allowed for extremely fast iterations, and its hierarchal model was very flexible and allowed you to work very fast and creatively. I'm surprised no one has had a good crack at re-creating the core functionality of Flash circa 2004, based on web tech, or something like Kha[1]. I've thought many times about starting such a project. I think the biggest challenges are developing a solid vector rendering runtime alongside the vector drawing tools, but

Thanks :) For the first point, yeah I agree, though I would still keep standard API documentation separated. And it gets "worse" when you add the 4th site: https://code.haxe.org which helps with 4th point (partly?). Tricky thing with guides like "how to make a game" is that it's not a haxe-specific thing; it's a haxe framework specific thing which they handle on their own: https://haxeflixel.com/documentation/, https://heaps.io/documentation/home.html, https://github.com/Kode/Kha/wiki (is there a better link for kha?), etc. There are links in https://haxe.org/use-cases/games/ but discoverability could likely be much better and include a generic "how to make a game" start point which points to either framework depending on your needs (2D/3D, mobile/desktop/console/web, etc.). Indeed Haxelib isn't visible :x Now that you mention it, we had