[oldmanhorton]

Lots of positive comments here that are mostly correct, but I will say that if you're working with more junior or just less technically passionate people, Starlark is a lot for them to wrap their heads around. "Python, but not", no Starlark.exe (always hosted in different exes that provide different functionality), poor editor highlighting/intellisense, and the concept of writing configuration in the same language which interprets that configuration are all hurdles that I've found some have difficulty with. DSLs encoded in yaml and JSON have a lot of the same problems, but I still get a lot of feedback that Starlark feels more complicated.

[placatedmayhem]

I agree with the difficulty of Starlark. I worked with Starlark a couple years ago to build some non-trivial things, which included writing custom Starlark providers. It was a gigantic pain. Documentation always felt very incomplete and finding existing examples were hard to come by (that has improved somewhat since I worked on that project, I believe).