Yes, this is all fair points. The problem I mostly have is I keep running in circles between the different possible ways this could grow. 1. It's a toy++ for

Yes, this is all fair points. The problem I mostly have is I keep running in circles between the different possible ways this could grow. 1. It's a toy++ for javascript developers. Kind of like Linqpad for .net. "You have a problem with your backend. No problem, fire up Jig, and you can interact with your stuff in a neat way." 2. It's a way for executives to get internal reports much faster than what they have now. 3. It's a way for spreadsheet-heavy institution to off-load some of their spreadsheet risk without investing millions in internal app development.