3,097 karma · joined March 8, 2011
You can reach me at ben at espresso.ai.
| It's not trying to target power users. They would learn VBA.
Most of our users know VBA and prefer not to use it. (Programmers who've ever tried VBA are familiar with its downsides; I won't go into them here.) Python is a significantly more productive language than VBA; our clients can typically write programs 10x faster in Python than in VBA. More importantly, a large class of programs that are trivial to write in Python using open-source libraries would take months or years of development time in VBA.
| It's not trying to target data processing. People who care enough would use a library like xlrd/xlwt.
xlrd/xlwt are very good for a subset of what DataNitro does: specifically, static processing (input and output) of Excel files. They don't support more complicated use cases (for example, building an interface to an external data source for non-technical end users, or a spreadsheet that runs analyses based on user input).
| It's not trying to go after big industries like finance.
We have a number of users in finance.
| It's easy to interop outside of excel and from within VBA
I wouldn't say it's easy, especially for people who haven't done it before. It'll certainly take more than two hours to figure out, at which point the license has already paid for itself.
| most hedge funds and banks have their own solutions already.
This is true, but internal solutions are frequently less flexible and harder to use than DataNitro; at the least, this makes them unsuitable for work done by non-developers (e.g. quants). It commonly saves developers time as well.
| This is specifically targeted to the casual people who want to do some in-Excel scripting but don't want to learn VBA.
Given the option, most people prefer to use Python over VBA; this is true even if (in fact, especially if) they know both languages.
| In that light, the product seems way over-priced (and probably should be in the $5-10 range) and unlikely to ever be used in a production setting.
DataNitro is used both in production and as a prototyping system by a number of firms.
Additionally, we don't wrap pyxll; we have a completely seperate architecture.
[1] See "The Unreasonable Effectiveness of Data", by Peter Norvig, Alon Halevy, and Fernando Pereira at Google.
Spreadsheet browsing is limited to a sample of the data (head + tail); you can set the size of the sample before pulling.
If you're in New York, I'd love to meet you in person at our Big Data in Excel meetup this Monday: http://www.meetup.com/DataNitro/events/149402612/
And, as the page says, we're looking for beta users! If you're interested in this, know someone who might be, or just have an opinion, I'd love to talk to you. You can comment here or reach me at ben at datanitro.com.
here's one example of an optimization: if you're using a basic Win32com script, it'll freeze Excel while it's executing. DataNitro doesn't do this, so you can turn a spreadsheet into an interactive dashboard just by using a while loop. it'd take a lot of time to get that working properly using Win32com.
(And, of course, there can be bugs - that is, mistakes - but there is no ambiguity.)
Planning to grow into something else is dangerous, though. To paraphrase Peter Thiel, you should be wary of building a startup that's a two-stage rocket. If the first stage works, you can and should stick with it; if it doesn't, you'll never make it to stage two.
what's wrong with the spreadsheet?