| I think phrasing spreadsheets as 2D code is mostly misleading, as it makes it seem like it's the code's 2D-ness that makes them useful. Spreadsheets are one way of consuming 2D _data_, which most business data is. They also provide a very easy interface for thinking about basic transformations on this data: the data is very visible, and every transformation you make is therefore very visible as well. Really: it means folks don't have to worry about control flow. I agree with other commenters as to the effects of 2D code. I've spent the past year talking to 100s of Excel power users, and it's pretty clear: at any scale, spreadsheets get incredibly hard to follow, audit, and maintain. The best of both worlds, IMO, is a spreadsheet for data visibility, and a program for transformation visibility. I'm a bit biased though, because this is exactly what we're building at Mito [1]. If you want to see more of our thoughts on the topics above - check out this blog [2] exploring the relationships between REPL environments, spreadsheets, and noteboooks! [1] https://trymito.io/hn
[2] https://trymito.io/blog/repl claiming that it's the code's 2D-ness that makes it beneficial |
1. What's the pricing model. I'm guessing it's not free or open source, but I can't even confirm that from the website. This is enough to bounce me from a product like this.
2. Is there reference documentation somewhere? I've been bitten before by enterprise products that only have getting started documentation, and I'm not keen to be bitten again.
3. I can find documentation for importing data, but not exporting. I assume it's available, but I can't quickly confirm it, and that feature is absolutely critical for the use case I have in mind. This sort of goes back to the reference documentation point as well...
Here's the use case I have in mind. My Mom, who is somewhat capable of programming but not an expert (anymore), runs a online plant store. As part of running this she has a bunch of scripts that transform one spreadsheet into another, e.g. combining a supplier price list, a list of images, and a bunch of data cleaning, into a csv that can be uploaded to shopify to create a list of products. Or turning a list of orders from shopify, fetched via json, into a spreadsheet that can be sent to the supplier as a single order.
Tooling that made this process simpler, easier to debug, etc would be (or have been) great (especially for me, the professional software developer who gets pulled in to help whenever things get too complicated). I took a look at this product with an eye towards that.
To be honest I'm not much of a sales lead, apart from the fact that the business is tiny, the software definitely isn't being rewritten during the summer (busy season), and it's probably not being ported to a new framework at all (why would it be, what exists works). Still, I'm curious about what your software can do, and if it would have been appropriate.