Only if customers don’t care about your labor practices. For me this story screams “Don’t Use or Recommend Atlassian - in fact, strongly advise against it.”
Like most modern languages, Rust has its own build system and package manager, Cargo. Everything you're referring to relates to that, and has nothing to do with LLM coding.
Edit: saw the clarification in another comment. But, in that case the essential point seems to be "I'm not familiar with something, therefore it's suspect."
You could say the same thing about AWS, GCP, OpenRouter etc. etc.
Databricks is near the bottom of the list that anyone who knows what they're doing would want to choose. It pivots every time there's a new technology and isn't really ever any good at any of them.
It punishes the inflexible deep thinker, perhaps. If you can’t figure out how to use an incredibly powerful tool to your advantage, how deeply are you thinking, really?
This is one of the pragmatic reasons that microservices can be a useful tool in a complex system. The enforced boundaries at every level - build, deployment, API, and team responsibility - make it easier to swap out, deprecate, or eliminate microservices than tends to be the case when the code is embedded in some larger context.
The point is that Github can’t fix it. It’s the user’s responsibility to not grant access to accounts that shouldn’t have access to the resources in question.
https://en.wikipedia.org/wiki/List_of_countries_by_GDP_(nomi...
…which lists India as #148, below countries like Zimbabwe, Haiti, Bangladesh, Cambodia, and Palestine.