I'm surprised by how many things that aren't that difficult or novel end up on the front page. CSV related projects come to the fore every week.

Heh, maybe I should start submitting some of my more trivial projects and rack up the HN karma ;)

i.e. "A testing utility for database migrations"

I explored this a bit (based off of the javascript-based http://sheetjs.com/sexql/) but the biggest difficulty is that people use CSVs and excel files in completely different ways for the same general task. In particular, different people set up budget workbooks in very different ways. There are also input problems and invalid files to deal with, so even if you manage to craft a meaningful integration you'd still have to figure out how to determine the structure and fix subtle non-uniformities

https://github.com/OfficeDev/Open-XML-SDK/pull/3 suggests that there are issues with use in mono

WebSQL is remarkably simple to use, works on the most popular browsers on mobile and desktop, and gives you the power of SQL. In contrast, IME indexed db felt like pulling teeth. The discussions seem to suggest that institutional intransigence by Mozilla pushed the internet back a step. (And yes, SQLite + Emscripten is significantly slower than websql on chrome and iOS Safari)

From a personal perspective I stopped building HTML web apps after I started to transition my WebSQL apps to IndexedDB. I really really disliked the experience (messy code/overhead) and haven't had any desire to write another with a client side DB again. The bright side for is however it drove me to learn iOS and Android development... not such a great day for the web though as I suspect my experience isn't unique.

Substack (yes, that substack) discussed this recently:

> a slick web page - this is very often (but not always) a sign of a library that put all of its time into slick marketing but has overly-broad scope and is very likely to become abandoned

http://www.reddit.com/r/javascript/comments/2378xo/the_best_...

Is there any indication that the posted link was already submitted? I would have expected some sort of warning.

There is a good reason why no one has unseated excel: it's easy to build the really easy 80%, but the last 20% is incredibly difficult and time consuming.

Excel only supports numbers that fit in an IEEE754 double, just like JavaScript.

There is some fancy logic to format numbers, however (including some mess for date codes). http://oss.sheetjs.com/ssf/ is a pretty decent implementation in JavaScript.

All versions of Excel have native support for integers.

http://msdn.microsoft.com/en-us/library/office/bb687869%28v=...

Excel supports 32 bit integers, which fit comfortably in IEEE754 doubles (there are 64 bit integers which cannot be exactly represented)

It's somewhat confusing. The structure is MIT licenses but the individual implementations have different licenses (for example, many functions were copied from OpenOffice (which is under Apache2 license)

It provides a set of JavaScript functions. It doesn't try to parse formulas. You probably could go back and define aliases for each function