4 ms·
Unless the software has nothing to do with each other. A client software in Java, another client in C#, another one in Obj-C and a server software in C++ will
by kuschku 10y ago
Unless the software has nothing to do with each other.
A client software in Java, another client in C#, another one in Obj-C and a server software in C++ will be hard to test together, will share no code, and often be developed in independent development cycles, often by independent teams.
Putting such things in monorepos would be stupid.
- ryandrake 10y agoTotally disagree. Any serious development project that has an application that needs to work across iOS, Android, Mac and Windows should be sharing as much of its business logic, in C or C++ which is usable on all those platforms. The UIs of course will be platform-specific, hopefully as thin as possible, but the majority of your code should be totally re-usable.
- deleted 10y ago[deleted]
- zellyn 10y agoDisagree. Typically, in this scenario, you're using some kind of protocol to communicate. In our case, it's protobufs: they are in fact one of the prime sources of breakages between repos, and one of the main reasons I wish we had a monorepo. Same would be true of json schemas, etc.
- deleted 10y ago[deleted]
- to3m 10y agoDisagree. If they're all part of the same system and/pr project, they ought to go in the same repo. Otherwise, you've not got one system/project at all - you've got several, and you shouldn't try to pretend otherwise. You can of course just press on regardless anyway, but that doesn't mean it's a great idea!
- jahewson 10y agoOh but it wouldn't. While those clients might not share code, each of them does share an interface with a common dependency: the server. Having the server code and a given client code in the same repo is what you want, which means you want the server code and all the clients in the same repo.
- zeven7 10y agoGoogle has code in C++, Java, Python, Go, and JavaScript spanning countless different products (Google has a lot of products), all in the same repo.