kittykatattack
commented
6 years ago No! 😄 I do not recommend using Hexi for any critical production work.
It needs many more active volunteers who can help with maintenance, and it would need to reach a stable version 1.0 before I could consider recommending its use for production. Although I use Hexi regularly in my day job (and, yes, I think it's awesome too!!), and it seems to be fairly bug free (?), I don't have enough time at the moment to do the regular weeding that it needs. It probably needs another 3 months of full time work to get it up to what I would consider production standard. When I, or a team of dedicated volunteers, is able to do that work and I feel Hexi is ready, I will let everyone know. 😄
DannyBen
flozero
Alright, I know GitHub issues are not typically meant to be used for such comments, but the README said "The Issues page is is Hexi's friendly chat room" ... so, here goes.
I am evaluating my options for HTML5 game development and Hexi is exactly what I was looking for.
I found out about it through your learningPixi repo, and my first concern about Pixi was that it only handles rendering and that the API is too verbose, so Hexi solves exactly these issues for me by smartly simplifying the APIs, and bringing more modules on board for sound, tweening etc. A really solid concept.
My only concern with Hexi, is that it seems to be a one man show, which makes it fragile. I guess it can be a lot of work to keep it up to date with each update of the libraries it encapsulates.
Also, I just noticed there is not much activity since 2016, judging by the code frequency graph... is it because its super stable?
Any words of reassurance on that subject? 🤞