Sincerely, your landing page gives you a very good impression about what spreadserve does and how sophisticated it its - but once you land on the server page it doesn't look as impressive. It works really good but I don't have the feeling I am given some superpower/I'm driving the batmobile.
Since then, I have always suspected it was still a problem in large financial institutions, although the few times I mentioned it to people they looked at me blankly. Now I feel vindicated!
Out of interest, does the Financial Industry use any analogues to source control and unit testing for spreadsheets?
[1] https://baselinescenario.com/2013/02/09/the-importance-of-ex...
Also one more question. Is it meant for server only or can it be used in a desktop app also? And if so does it require an install on the machine or can it be used just by copying the assemblies in the app folder?
I realised that we can escape that frustrating cycle by building a server runtime for spreadsheets. Just as node.js took JavaScript to the server side, SpreadServe is "node.xls": an asynchronous scalable server side runtime for Excel spreadsheets that supports XLLs, RTD & VBA as well as a REST API, RDBMS integration and websockets subscribers. As Felienne says [3] "spreadsheets are code". But that code is trapped in a desktop IDE for grid based visual functional programming: Excel! And that's not the right environment for reliable automated operation. So SpreadServe's aim is to separate the development and rumtime environments for calc heavy spreadsheets: Excel for rapid change cycles by tech savvy power users like traders, then SpreadServe for production scalability, resilience and audit logging.
[1] http://spreadserve.com
[2] http://babbingtonslade.com/industries/
[3] https://etrading.wordpress.com/2015/08/13/spreadsheets-are-c...