We've walked a fine line between fixing bugs, adding the features that our users have asked for and building out the BI interface we think the world should be using in 5 years.
We don't always get it right, and I'm sorry if we broke things for you on the performance side.
We will be spending a few of our development cycles after 0.33 to try to clear out our bug queue.
One specific factual point I'd like to reply to however -
SQL isn't going anywhere. If anything we're making it easier to both write plain SQL, use SQL templates or use our graphical interface on top of SQL query results in our next release (preview at https://github.com/metabase/metabase/releases/tag/v0.33.0-pr...)
I’ve been using Metabase off and on in prod since 2016. I think you guys are really onto something and I love seeing Clojure in a popular OSS project. I know you guys just got some money; here’s my pitch to make it count: Metabase would be a lot more sticky if you provided a robust home for annotation and discussion. You’re better than most at letting admins describe data, but often users want to talk about the data they are discovering. Doing so in the context of the data is so much more effective than talking about it in generalities in Slack. I think Yellowfin has some features around discussion but there is always room for improvement. Maybe one could: Comment on a data point, write an explanation for why a date range has weird data, or tag a colleague to ask about an outlier in their dept. Celebrate wins with emojis? All I know is that there is nothing stickier or more engaging than discussion history. Keep up the good fight!
While I have you here...
<nag>
bump for the Athena driver. Also I can’t use Metabot without some privacy settings. Can’t anything be done? </nag>
We've walked a fine line between fixing bugs, adding the features that our users have asked for and building out the BI interface we think the world should be using in 5 years.
We don't always get it right, and I'm sorry if we broke things for you on the performance side.
We will be spending a few of our development cycles after 0.33 to try to clear out our bug queue.
One specific factual point I'd like to reply to however - SQL isn't going anywhere. If anything we're making it easier to both write plain SQL, use SQL templates or use our graphical interface on top of SQL query results in our next release (preview at https://github.com/metabase/metabase/releases/tag/v0.33.0-pr...)