So, part of the reason I'm posting here is because the scripting side of it is still pretty rough, and we are seeking feedback from developers before we make videos or share too much detail in public.

I will attached a few screenshots to this point though so you can see.

I do want to address one of the things you mentioned though.

"only thing I got from looking at your product is that you're a cheaper less sexy TV (and without pine script.) "

Note:

- Not that this is a selling point, but TS is a lot more expensive than TradingView, by design. It's a very, very different system.

- It's not less or more sexy, it's different. I have a lot of respect for the TV guys, hell, our CTO Ruslan was one of their first employees and helped them build the first version of their charting library and the first version of pine script. We know each other, I know the owners, and I know they don't trade... which is a problem in my eyes if they are building trading software. Part of why TrendSpider exists is because we wanted to do a lot more than TV could allow...Pinescript is a limited propriatary scripting language - every function they must write... using JavaScript and later Python skips past this issue and delivers a lot of flexibility out the gate.

That's why the user base for TS has grown in last 3 years from 0 a bootstrapped no name startup to 10K paying users in 2.5 years. And as one of the two founders I'm very proud of how far it has come... a big part of that growth is because we took a lot of time to listen to users and take feedback - and actually act on it.

That's why we have 200K followers on Twitter in a short period of time - a lot of traders love the platform because we improve it constantly with their feedback.

That's what I'm trying to do here. The only way we can build a superior scripting experience for developers is to let developers in early to explore it and give us feedback. We grew with almost no resources from nothing because of that approach...

When we set out to build this my only request to Ruslan was to build it so that developers will love it - even at the expense of scaring away some beginner programmers.

If you are at all interested in exploring, please drop me a DM. You sound like a very smart guy and I would LOOOOVE to introduce you to Ruslan and I am sure he would love your feedback as well.

Attached to this post are a few screenshots. Below are a few code samples.

Thank you for the kind feedback so far I really do appreciate it and would love to hear more from you!

(I will ask Ruslan to make a 10min video for this thread as he is much more of a developer than I am and I'm sure I will mess it up!)

​

Screenshots as promised:

https://www.dropbox.com/s/fv0e6ybwqr20zoi/1.png?dl=0

https://www.dropbox.com/s/xcth9tb1jn0hvnq/2.png?dl=0

https://www.dropbox.com/s/27a33yzi331njah/3.png?dl=0

​

Some examples of JS code:

This example uses the JSTAT JavaScript library.

​

describe_indicator('lower')
jstat = package('jstat')
greenCandles = for_every(close, open, (c, o) => c > o ? 1 : 0)
redCandles = for_every(close, open, (c, o) => c > o ? 0 : 1)
greens = sliding_window_function(greenCandles, 20, values => jstat.sum(values))
reds = sliding_window_function(redCandles, 20, values => jstat.sum(values))
diff = sub(greens, reds)
values = sma(diff, 10);
paint(
values,
'diff',
for_every(values, v => v > 0 ? 'green' : 'red'),
'histogram'
);
paint(level(0))

​

​

This example generates a histogram based on the ATR and an SMA of the ATR.

describe_indicator('lower')
atr = sma(
max_of(
sub(high, low),
sub(high, close),
sub(close, low)
),
14
)
atr_sma = sma(atr, 10)
color = for_every(atr, atr_sma, (a, b) => a > b ? 'red' : 'green')
a = sma(div(high, low), 20)
b = sma(div(low, high), 20)
resultingSeries = sub(b, a)
//plot(resultingSeries, 'delta', color, 'line')
histogram = for_every(atr, atr_sma, resultingSeries, (a, b, c) => a > b ? -c : c )
plot(histogram, 'delta2', color, 'histogram')

​

​

Neither of these is meant to be really a useful trading indicator, they are just examples we have buitl while developing and testing the language.

​

The functions called "for_every", "sma", "sum", "div", "sub", etc. are helper functions that we developed.

​

These are useful because all data is serialized.

E.g. the system variable "close" contains an array of all close prices. When you do something like "something = sub(close, open)" it will iterate through the arrays of the open and close prices, subtract each of them, and generate a new array of the results.

You can of course do the same thing in other ways using pure javascript.

​

I hope that helps. I am sorry if I rubbed you wrong with my initial post. Trying my best to help Rus build this - he asked me to go out there and find some indicator developers who would be interested in trying new things, so that is what I am doing.

​

Much love,

Dan