41–50 of 131 posts
Gorgeous work — and from poking around in the console a bit, it looks as though you're using the latest version of Backbone.js. Any interest in having Airtable featured on the list of example apps on the Backbone homepage? If yes, drop me a line...
Couldn't find your email listed (PS your site ashkenas.com seems to be down right now). Can you email me at howie @ airtable.com?
Here's one use case: i tried importing a 500+ row wine spreadsheet into it (it has columns like type, producer, name, vintage, rating, source etc). I had to save the file as CSV and import it -- or at least that's what I thought, but filepicker seems to support picking from google drive. I don't know if it would have accepted a spreadsheet. Your app seems sluggish to scroll compared to Google Docs at that size, and t…
Thanks a lot for your feedback, these are definitely things we're looking to tackle. We're planning on improving scrolling performance soon, it's definitely a priority for us to improve our performance for large datasets. As for the linking, we definitely want to do more to help you normalize your data. We can also infer column types to help with the import process. Doing this type of thing on paste is an interesting…
Edit: reach me at shri (at) freshvc (dot) com
The "instantly syncs updates with all users" bit caught my eye. I always wonder how people go about implementing that. Asana works that way, and they have their own framework named Luna that does some functional reactive magic. Meteor, which I've been working with a lot lately and have really enjoyed using, was also created by some ex-Asana people, and enables the same type of real-time synced updates. I was just won…
We've closely followed the developer blogs of both those projects (and in Meteor's case, their source code). With those learnings, we built our own realtime database engine that supports relational data (which Meteor doesn't yet support) and also some other major features like the ability to undo any user action out of order (like git revert), which is necessary to support undo in a multi-user context (because the last thing that you did may not be the last change globally if other people are concurrently making changes). Undo is a particularly challenging feature to implement in a structured relational database context, because it can't be reduced to a set of simplistic character insertion operations as is the case for a google word doc, or a spreadsheet (which is a simple 2d array of values without type constraints, foreign key relations, etc).
One complaint: Referring to your Basic plan as being "Free forever" is a bit disingenuous. In my opinion, the FTC ought to prohibit use of this term by tech companies located in the 650 and 415 area codes.
can you tell us more about the stack used?
Well-polished product.. can you u talk a little bit about the design and the front end. what did you use for the UI design and front end. it is clean..
Earlier quoted context omitted.
Thanks a lot for your feedback, these are definitely things we're looking to tackle. We're planning on improving scrolling performance soon, it's definitely a priority for us to improve our performance for large datasets. As for the linking, we definitely want to do more to help you normalize your data. We can also infer column types to help with the import process. Doing this type of thing on paste is an interesting…
If you're interested in talking about the challenges of creating a performant spreadsheet, I've built a javascript-based spreadsheet backed by a database that's more performant than Google Docs/any open source table available on the internet. I'd be happy to share the techniques. Edit: reach me at shri (at) freshvc (dot) com
Impressive! can you tell us more about the stack used?
See more in my other comment: https://news.ycombinator.com/item?id=8374468