3 ms·
A lot of talk about this being aimed at "non-technical" people, but these types of interfaces are still widely needed for developers, too. It can make trivial
by nkozyra 11y ago
A lot of talk about this being aimed at "non-technical" people, but these types of interfaces are still widely needed for developers, too. It can make trivial jobs much, much faster to complete both programmatically and through a GUI. Technical folks like abstractions too!
I like this quite a bit, although the similarity to SQL might pose more problems than it's worth in the long run.
That and AmazonML's striking similarity to Excel/CSV (not to mention the crop of ML-on-demand providers) show these types of interfaces and user experiences are a pretty glaring need right now in data science / ML / classification.
- murbard2 11y agoBy non-technical I think they largely mean "non-statistician" rather than "non-developers".
- jghn 11y agoI saw them present a while back and someone in the audience asked "why SQL" stating that all innovative projects like this end up coming up with their own query language. The response was that everyone knows SQL so it's easy to get started and that they want to enable access from environments like Python and R for more advanced querying.
- murbard2 11y agoIn addition, SQL design is simply really good. It's of the few successful declarative language: you get what you describe. It's also a total, in that all programs terminate. These are really good characteristics to have.
- nkozyra 11y agoSQL is really good. My issue is you run into inconsistencies in the way you expect a function to work (when they're shared semantically across SQL and BQL in this case) and that eventually leads to confusion. Like working in the Arduino language versus C.