Build systems - no. The people who maintain the build systems - yes. You might see them add a script here or there that ends up being "critical", either for telemetry/logging or investigating state at some stage of a build.
I can only rationalize these things happening as inexperience, too eager to please. I'd hate for these things to occur only for job retention tactics for the increased bus factor. But they are very much so real.
I've seen it happen in multiple instances with moves to generalized development containers/workspaces.
> You might see them add a script here or there that ends up being "critical", either for telemetry/logging or investigating state at some stage of a build.
I don't see how that translates into gen dev environments either.
I would love to see the use case for a dev env that requires OMP (or OMZ, or Prezto, or even Starship) to be a functioning dev env.
Well, revealing my previous employer, Microsoft, many devs there love oh-my-posh for whatever reason. I have no idea if its still the case anymore but I distinctly remember it being a thing for a few dev-div repos for a while, definitely in BI/analytics/dynamics, and some places in SQL.
If you don't think I'm reputable, you can go and ask the man who made oh-my-posh where its actively used in his company and why.
You can also ask someone who works in any of those orgs if oh-my-posh makes an appearance and what happens if you try and remove it from the standard checkout/build process the average engineer goes through.
As for specifics, can't help you there, I was never the person who added the dependency. And I am distant to the acute requirements for oh-my-posh were, if there were any (which I am absolutely confident there was not, but an inexperienced/misinformed engineer could conjure about any number of reasons). I know specifically my short interactions with BI specifically trying to rid myself of oh-my-posh through regular uninstall + blackholing the download would lead to failures.
I can only rationalize these things happening as inexperience, too eager to please. I'd hate for these things to occur only for job retention tactics for the increased bus factor. But they are very much so real.
I've seen it happen in multiple instances with moves to generalized development containers/workspaces.