Feels very similar to JSON RPC.<p>This isn't a script at all but a way to call an RPC method. And over a non duplex connection at that.<p>I often use something very similar with a few additions to support callbacks. Add an ID field so that responses can be matched and you suddenly support calls being made over a duplex connection such as Websocket or TCP connection;<p>Shorthand and longhand formats complicate things so stick with one type. The whole $ prefixed params are also un-needed, especially if your'e expecting them and have the important values under your own expected keys anyway.<p>But then after all this you start turning into json-rpc.
This exact concept has been done multiple times. And it never worked, because the syntax was horrible. And it's just not convenient at all, it's good for toying around with interpreters and the likes but it has no purpose or use. See <a href="https://m.reddit.com/r/coding/comments/3akmn1/sums_this_rel_thing_up_pretty_well/" rel="nofollow">https://m.reddit.com/r/coding/comments/3akmn1/sums_this_rel_...</a>
This reminds me of my multiple attempts in writing a declarative scrapper framework. In the end, I've chosen to just write the code.<p>What I see is a crappy ad-hoc scripting language. I feel bad saying so, but I can only view this project as a bad solution to whatever problem you have.<p>You could have chosen to send actual code, be it JavaScript, Python, Java or even Linux binaries, executed with limited privileges. How would that look like? AWS Lambda.
I like the problem you are trying to solve and I like the idea of the JSON data structure but I am not so keen on the language as JSON. I find it hard to read, which would be worse in more complex real-world examples.<p>I guess I would like to see the code as plain text. Packaging all the data to send as JSON is OK, and the code could be text in a single JSON data element.<p>Post a story to Hacker News once you get some experience using JSONScript with some feedback on how you went and how the idea evolves.
This technique never ends well. When your service interface is some untestible semi-script language your clients will hate you.<p>Nice work on building an interpreter, but I'd throw the entire SOA book at you for deploying this in a production environment. I haven't even addressed stability, latency and load of programmable Web interfaces, or security.
You can use it via the middleware for Express to implement advanced batch processing in a single line of code.
<a href="https://github.com/JSONScript/jsonscript-express" rel="nofollow">https://github.com/JSONScript/jsonscript-express</a>
I think it's a cool proof of concept and you tried out a bunch of ideas that could work, but I don't think you should use this approach for anything. JSON is not conducive for encapsulating complex logic, and it shows. Who is going to write and maintain that spaghetti code? Anyway, code execution at the datasource, is not a new problem, and there are approaches to solving it. Redis for example allows you to upload and execute Lua scripts at the source - way easier, way more readable, makes infinitely more sense. So why not use Lua or just use JavaScript - since your front-end code is all JavaScript anyway?
Thanks for all the comments, some are really useful. JSONScript is an interesting experiment and the time will show whether it's useful and whether we use it. What I find really interesting is why most higher level abstractions that reduce the amount of code to be written polarise normally friendly people to such extent, and "just writing code" is seen as the only "sane" choice. On the other hand, tools that increase the amount of code are usually very welcome. Any idea why it is happening?
If you write it all in arrays, then you can reuse Cirru's text syntax and would look shorter, hope you are interested:
<a href="http://cirru.org" rel="nofollow">http://cirru.org</a>
I know this thread is dead at this point, and any rational argument is probably lost on the author,
epoberezkin, but this has made me think of BobX:<p><a href="http://thedailywtf.com/articles/Classic-WTF-We-Use-BobX" rel="nofollow">http://thedailywtf.com/articles/Classic-WTF-We-Use-BobX</a><p>The scariest part is that epoberezkin has mentioned using this new innovative language at his job. I hope someone stops him.