News for hackers. Stuff that matters.
Re:Memory usage of a toy C# server and client with 500K conc... by iainmerrick on Saturday January 26, 2019 @06:36PM (#19009294)
No, they are correct, the tooling is bad. Tooling in the sense of setting up a build for a large and complex project, that can resolve dependencies quickly and correctly, where the build is very fast and deterministic, where incremental builds always work correctly, where building multiple configurations is easy and reliable, and so on.
Re:Memory usage of a toy C# server and client with 500K conc... by gameswithgo on Saturday January 26, 2019 @08:59PM (#19009941)
what has good tooling for that?
Re:Memory usage of a toy C# server and client with 500K conc... by noahl on Saturday January 26, 2019 @10:13PM (#19010159)
I believe the state of the art is bazel and similar systems. Bazel supports C++, Python, Java, and Go well that I know of, maybe more too. It's also extensible, and people have rolled their own support for various languages. You can find some custom bazel rules on GitHub.
Re:Memory usage of a toy C# server and client with 500K conc... by slavik81 on Sunday January 27, 2019 @04:01AM (#19010974)
Bazel is an interesting build system, but it worries me that there are TensorFlow releases from 2018 that won't compile with Bazel clients from 2019 without adding extra flags.
Re:Memory usage of a toy C# server and client with 500K conc... by slavik81 on Sunday January 27, 2019 @11:08PM (#19015275)
Correction: December 2018, not 2019.