←back to thread

392 points mfiguiere | 5 comments | | HN request time: 1.057s | source
1. kylecordes ◴[] No.35477308[source]
The essential characteristics of Buck2 look very appealing - but it's hard to see this catching up with the substantial ecosystem of language support rules for Bazel.
replies(1): >>35477685 #
2. hn_go_brrrrr ◴[] No.35477685[source]
If the language rules are all Starlark, shouldn't they be compatible?
replies(2): >>35478614 #>>35478758 #
3. dikei ◴[] No.35478614[source]
Same language does not necessarily mean Buck2 will provide the same API as Bazel to write language rules.
4. EntrePrescott ◴[] No.35478758[source]
Haven't looked at the Bazel codebase, but it would strongly surprise me if the language support rules were implemented in Starlark. More likely, I'd suppose them to be almost exclusively written in Java (and highly based on quite Bazel-specific classes), with Starlark only coming into play in the form of bindings for being used by the users for their BUILD/bzl definitions.

Edit/Add: cf the part about language rules in this comment from a person who says they're a former bazel developer: https://news.ycombinator.com/item?id=35477309

replies(1): >>35479151 #
5. hn_go_brrrrr ◴[] No.35479151{3}[source]
Only the C++ and Java rules are native, the rest are Starlark. I don't know Bazel internals so I can't really comment on your point about APIs.