ajoski9

check out https://0sql.io .. Hosted version is available if you want

does this engine compile sql or just provide context in a structured way?

Would a semantic layer integration into JetBrains help here?

hey everyone, we just launched a live demo site: https://demo.strata.do

So you don't have to setup docker if you just want to try the product directly. Thanks!

Let me guess, it's the boring stuff.

You can now try it live with zero setup: https://www.0sql.io/try/

The article didn't explain how a well organized civilization couldn't reap the benefits of a new technology faster. Guns were fairly decentralized tech. Civilization didn't collapse.

Sure but wouldn't and organized kingdom have the resources to scale up iron weapons production faster? They certainly had larger armies I would imagine.

so economically speaking it was cheaper to mass produce iron weapons.. I would have assumed a first mover advantage. It would be surprising if iron tech sprung up everywhere at the same time. And sure smaller groups could do it, but some groups would do it better,faster, cheaper (paretto principle). They should have had a material advantage me thinks. Since its cheaper you could arm more people perhaps. Lastly, the current powers could have also adopted iron and armed larger armies.

Why didnt the people who mastered iron just conquer and continue civilization? Like we see with every other case where there is a tech advantage.

Thanks for the heads up. I do have a specific question on your implementation. We were thinking about launching a semantic layer as a service api. You post your model and we give you fast query generation. You can then use this in your own tools. Benefits are a fast expressive semantic layer, model hosted, and your actual data stays behind your firewall. What do you think of this?

Great question. Semantic layer has been around before I was even in the industry. Probably late 90's. Innovation on this layer has gone backwards actually. Simpler and less capable (Looker vs Strategy for example).

It does however improve on agent performance in one important way: rejects plausible queries that are invalid. Agents writing sql are more likely to be inventive in unexpected ways. Business users won't know the difference. It is definitely not useful for developers/data engineers anymore. But quite a good tool as part of analytics harness for business users.

The one issue with Snowflake semantic dialect is the lack of expressiveness. Agents have to route to sql for many common scenarios. What do you think?

ah man, that's not cool

Good point. Should've linked to the main page. Thanks

Thanks a mill for that! I meant to keep try in the body only.

Thanks for the comment. We are highly focused on certain use cases and want to be upfront about that.

Agreed. Also pretty to look at IMHO

Is that true. Feels like new Ruby versions and great updates are being churned out relatively fast these days.