A co-creator of Pathway here - noticed some inbound from the HN link and was a bit shocked to see the discussion. Of course, Airflow is one of the most widely used technologies out there, even if sometimes considered part of the "legacy" orchestration stack.

For software that is anything other than a modifiable template, stars and forks typically serve users as bookmarks. In the distant past, forks were the prevailing bookmark mechanism. Users who joined Github long after the star functionality was added generally prefer stars over forks for bookmarking. Personally, when evaluating current production use of a project, I index most strongly on the count and type of issues raised.

As for the Pathway framework specifically, if you dive in, the star-gazer demographics is split roughly evenly between: (A) folks, like parent, who heard about the tech one way or another and thought it was cool enough to engage with; and (B) participants of bootcamps and hackathons based on this framework and run in partnerships with top-tier universities globally. The license also restricts forking, and is less welcoming to external contributions than Apache projects.

Clearly this means new SaaS companies need to start buying forks, issues and PRs for their repos now too.