4 ms·

Let's make the snarky comment into a helpful comment. Why do you think it shouldn't exist?

by solarmist 5y ago

speedgoose 5y ago
Monorepos create more issues than what they solve.
- tsimionescu 5y ago
  So the Linux devs have no idea how to properly use Git?
  - speedgoose 5y ago
    I'm not sure whether the Linux kernel git repository qualifies as a Monorepo.
    - tsimionescu 5y ago
      Of course it does. It includes core kernel code, drivers, countless libraries (compression libraries, fonts, a unit testing framework, various data structure implemetations, and many many others), file systems, network stacks, a programming language runtime+compiler (ebpf), and many other subsystems. According to multi-repo advocates, it would obviously be split up into at least a dozen different repos, with dependency management tools to specify which version of zlib or ebpf to use, with a dedicated repo just for the build logic, of course.
- solarmist 5y ago
  Such as? That's just parroting “common opinion” otherwise.
  - speedgoose 5y ago
    The second paragraph of the article we are discussing about for example. But you can find a list on Wikipedia and make your own opinion : https://en.m.wikipedia.org/wiki/Monorepo https://en.m.wikipedia.org/wiki/Monorepo
- tambourine_man 5y ago
  Supporting evidence?
  - speedgoose 5y ago
    The Wikipedia article about monorepos has a good summary https://en.m.wikipedia.org/wiki/Monorepo https://en.m.wikipedia.org/wiki/Monorepo Then you can do your own opinion, I'm sharing mine.
    - jeremyjh 5y ago
      Apart from performance issues that article offers more (and more significant) advantages than it does drawbacks, so it really does not support your statement.
- ratww 5y ago
  That's completely false. Monorepos don't really create issues at all when done properly, and when used in situations where they make sense. In smaller scales, for example, they're fantastic for productivity, and my company is not looking back.
- jeremyjh 5y ago
  This is no different from saying "monorepo bad". Aside from performance issues in git, why would a monorepo be bad? It seems very natural to me to have a whole system referenced with a single branch/tag that must all pass CI together. Otherwise supporting projects can introduce breaking changes downstream that are not apparent before they hit master.
- anaganisk 5y ago
  Somehow its working for google? May be im wrong but last I heard they use mono repos.

Let's make the snarky comment into a helpful comment. Why do you think it shouldn't exist?

speedgoose 5y ago

Monorepos create more issues than what they solve.

tsimionescu 5y ago
So the Linux devs have no idea how to properly use Git?
- speedgoose 5y ago
  I'm not sure whether the Linux kernel git repository qualifies as a Monorepo.
  - tsimionescu 5y ago
    Of course it does. It includes core kernel code, drivers, countless libraries (compression libraries, fonts, a unit testing framework, various data structure implemetations, and many many others), file systems, network stacks, a programming language runtime+compiler (ebpf), and many other subsystems. According to multi-repo advocates, it would obviously be split up into at least a dozen different repos, with dependency management tools to specify which version of zlib or ebpf to use, with a dedicated repo just for the build logic, of course.
solarmist 5y ago
Such as? That's just parroting “common opinion” otherwise.
- speedgoose 5y ago
  The second paragraph of the article we are discussing about for example. But you can find a list on Wikipedia and make your own opinion : https://en.m.wikipedia.org/wiki/Monorepo https://en.m.wikipedia.org/wiki/Monorepo
tambourine_man 5y ago
Supporting evidence?
- speedgoose 5y ago
  The Wikipedia article about monorepos has a good summary https://en.m.wikipedia.org/wiki/Monorepo https://en.m.wikipedia.org/wiki/Monorepo Then you can do your own opinion, I'm sharing mine.
  - jeremyjh 5y ago
    Apart from performance issues that article offers more (and more significant) advantages than it does drawbacks, so it really does not support your statement.
ratww 5y ago
That's completely false. Monorepos don't really create issues at all when done properly, and when used in situations where they make sense. In smaller scales, for example, they're fantastic for productivity, and my company is not looking back.
jeremyjh 5y ago
This is no different from saying "monorepo bad". Aside from performance issues in git, why would a monorepo be bad? It seems very natural to me to have a whole system referenced with a single branch/tag that must all pass CI together. Otherwise supporting projects can introduce breaking changes downstream that are not apparent before they hit master.
anaganisk 5y ago
Somehow its working for google? May be im wrong but last I heard they use mono repos.