> One of my major trouble with haXe is the adoption. > I don't imagine for now giving an haXe project to an another team. > They will be completely lost.
Why ? I think people often underestimate the capabilities of people to learn new things, and to enjoy it ! haXe not a complicate programming language, and the minor adaptation time it needs is very rewarding since it will make your whole daily-coding experience a lot better. > So the last point is, as nobody never take mtasc further (mainly > because ocaml seems not to be appealing), the continuation of haXe, > eventhough Nicolas said is motiontwin will continue on it. It's IMO a > great risk that it is a one maintainer only project. > Everyone knows mtasc is in a very stable and efficient status. > But haXe is another deal… In its current status, I would say that haXe is as stable as MTASC. Except 1.0 to be even more stable than current MTASC since the compiler is designed from scratch based on both MTASC and MotionTypes experiences so uses a lot more stable architecture. Nicolas _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
