mdupenois

Very cool, really like the DSL, eminently readable.

1) Just pushed an update to fix that, thanks for pointing it out.

2) Syntax checking has been a big discussion point for us, we would love to be able to limit people to only valid blocks but also didn't want to have a giant block of validation javascript to deal with the drag and drop on the blocks. As for error messages, you're totally right; they're massively lacking. Difficulty is that we keep changing the way we're storing rules as we learn more about what users want to do, given that we didn't want to have to build a proper syntax parser until we had a more stable concept of how they'd be structured.

Out of interest, what sort of error message would be useful? As in, how technical e.g. "I don't understand how to if moving_avg > buy" or "There is an error at 'if moving_avg > buy' returns: Nil expected: boolean"

Hacker news has throttled Rob's replying (too fast), he says:

Thanks for the great feedback. We've just pushed an update that tries to clarify by removing "One time payment" and removing the "every area of Quantblocks" language.

Thoughts?

Hah, yeah, unfortunately the legal team at the incubator we're in suggests we might not survive too long as a company if we go down that route :)

It's funny that you mention it because, as Rob said, we've been playing with the idea of adding a competitive edge, but the commissions is a cool idea. We were also considering a kind of achievements approach as well as a leaderboard but want to try and keep the idea of it as a tool as opposed to a toy.

Love the data idea, in fact surplus of data is already a bit of an issue; we're running out of screen real-estate.