Noury Bouraqadi-2 wrote > The main difference is that with PharoJS we develop and test in Pharo, > with the confort of all cool tools such as the GT inspector, spotter :-)
Wow!!! That is my main pain point with Amber. Unless one is very disciplined with TDD, the linkage between the app loaded in the browser, and Helios loaded in a separate window, introduces a run-compile-like cycle where after every change, one has to reload the app which reloads the IDE, and you lose all current state e.g. workspaces, etc. How mature is PharoJS? Is anyone using it in production? Who are the core developers? What are the intentions e.g. toy? experiment? production-quality? next big thing? ----- Cheers, Sean -- View this message in context: http://forum.world.st/PharoJS-tp4837593p4837974.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
