This is very interesting. I was actually looking for a cleaner way to write SQL and Python code. I find writing multistring SQL query on Python code messy so looking forward to giving DataStation a shot.
Couple of question-
- Are you building this as a pure Open Source project? I couldn't find the pricing section, and you have built it as an electron project. I am curious to know about your pricing strategy.
- Have you considered incorporating dbt or dbt like syntax query?
> - Are you building this as a pure Open Source project? I couldn't find the pricing section, and you have built it as an electron project. I am curious to know about your pricing strategy.
Long-term plan is that everything currently open source will always be open source (and there's quite a lot I believe). I'd like to release a hosted (paid) SaaS version for teams and an enterprise version also aimed at teams.
But the desktop app that exists now will always be free and open source. And I have no plans to stop adding new databases, file sources, and scripting languages as needed to the open source core.
> Have you considered incorporating dbt or dbt like syntax query?
I think it's already pretty close to this. You can import data within SQL queries (works with SQLite, MySQL, and PostgreSQL) using the `DM_getPanel` syntax. For everything else you can use Jinja-style templates [0]. This allows you to, for example, run a query to select IDs based on some filter in a PostgreSQL database and then pass those IDs to an Elasticsearch filter in another panel -- without writing any code.
I just use the "future" slack sdk for this. It uses deno, rides on the slack auth, and has a little DB in there for storing config and state if you need it. Slack itself provides basic but sufficient UI tools.
I don't know if in practice this is really the same as what OP is providing and it's tied to slack which is abstractly bad. But if you're already working in ts and running slack it's very powerful for how easy it is.
Can you say a bit more about what you mean? Are you talking about this: https://api.slack.com/future? If so, I'm not sure how it relates, but maybe I'm missing something?
I'm more likely I'm missing something, or assuming the main use of windmill is similar to how I use this, when it's just a small overlap.
The problem I needed to solve was how to enable employees outside of engineering to run scripts written by engineers, without them having to set up/interact with a full scripting environment like node. Particularly managing secrets and auth was a problem.
That slack "future" thing makes it very easy to drop a js or ts script into a new "workflow" and push it into the slack org. You can attach it to a slack modal or form, have auto-complete hints, just generally piggy-back on the slack UI that everyone is already familiar with.
It's basically deno with the slack UI over it from the user's perspective.
Again I don't know if this solves any problems people would be using windmill to solve, but if I were using windmill I'd probably be using it for something similar to this.
