4 ms·

these tools only work if you are big. small companies probably will never need bazel. the dependency management is just aweful and not all languages are equally

• gravypod 5y ago
  > dependency management is just aweful There is active work to improve this and make external does a first class feature. It will improve as more external contributors work on solutions and adopt bazel. > not all languages are equally well supported Similar to the previous statement. It doesn't make sense to imply "it's not perfect so it will never be perfect". The vision and feature set makes sense to me and I see no other build system tackling this scope. > and for small shops it's probably stupid to add build files everywhere. What makes it stupid? If your team is so small that you're only building one binary you only need one BUILD file. Very similar to how Gradle works actually. Also, build files are mostly auto generated if you wire your source code to standard conventions. It's something you only need to think about or touch when doing something complex (that also is not supported by other build systems). Example: using genrules to automate something or packaging things for deployment. If you have: - more then one language - unit tests - package an artifact for deployment (Docker, tar, zip, etc) - can benefit from caching Bazel-likes are pretty much the only option right now. There are quirks but there's also a growing community trying to smooth out those areas.