Random thought: As a mostly self taught engineer, I've always had issues with people referring to minified, transpiled, bundled javascript as a "binary".
I know this is my own definition, but to me if it's not compiled to binary, it's not a binary. I seriously think about it every time someone says "binary" in relation to production javascript bundles.
@thePunderWoman That's a #Bazel thing, and not really a common term. I think many Nooglers get just as confused regardless of background.
Even the internal Bazel docs concede that it's a misnomer. It's just called that to algin with `go_binary`, `java_binary`, etc.
@develwithoutacause I don't know if that's it. I've heard so many googlers use this that are unrelated to bazel... even long term Angular team members. But yes, bazel doesn't help.
@thePunderWoman I guess #NPM does use "bin" as referring to executables, which is kind of the same mistake? Though that's usually not used when referring to a build output.
@develwithoutacause You might say they're putting the terms all in the same...bin?
@thePunderWoman Ok, true story related to this:
I got my programming start in #VisualBasic and when I first started adding assets to an app I didn't know where to put them and didn't understand the directory structure or file path resolution.
I found the "bin" directory which contains the built executable in #VisualStudio and interpreted that as "a bin or container of all your files", so I dropped my assets into there.
This was also before I learned about source control, so thank god I didn't know how to clean a project, or else it would have deleted all my assets too. I had no idea how dangerously I was living...