PRQL at Three Years

[richb-hanover]

The first commit for PRQL was 1 January 2022. The current implementation has remained remarkably true to the original vision. Here's the README from the initial commit: https://github.com/PRQL/prql/blob/8ddc6e0dcdbccf88465650571c25c7fb4ba13f28/README.md

It has now been three years since that first commit. Perhaps it's a good time to reflect on our progress.

I propose we pick an upcoming Sunday to take 60-90 minutes to review our accomplishments, talk about work that is in the pipeline, and discuss "what's on the horizon". We could find at a convenient hour, perhaps the same time as the regular PRQL Fortnightly Dev Call.

My questions:

1. Would this be useful?
2. Sunday, 5 January 2025 is the next regularly-scheduled Dev Call at 10:30am PST, 12:30pm EST, 6:30pm CET. Would that date and time work? Should we look for a better date/time?
3. What topics would be relevant?

I look forward to talking soon. Thanks!

@max-sixty @aljazerzen @snth @vanillajonathan @eitsupi @PrettyWood @kgutwin @anybody-else

[aljazerzen]

That seems fitting. The development has slowed down a bit, so it might be time to rethink the roadmap and set the endgoal for PRQL 1.0.

The main question we talked about with @max-sixty is whether PRQL should focus on being a query language preprocessor or a full standalone language. The difference between the two is subtle, so it would be hard to explain here.

The regular dev call slot is ok with me.

[snth]

Thank you @richb-hanover for this initiative. I think it's a great idea to take stock.

The timeslot is not great for me but I will try to make it this week for this discussion.

I have quite a few reflections and will try to write some up ahead of time.