News for hackers. Stuff that matters.
Re:Our Machinery Guidebook by contingencies on Wednesday July 06, 2022 @12:22AM (#31996681)
we use C/C++ for everything. This includes things like command-line tools and documentation generators which would be tempting to write in a scripting language, such as Ruby or Python.

Ahh, great. Move along...

Re:Our Machinery Guidebook by Yax on Wednesday July 06, 2022 @07:56AM (#31999584)
From business point of view it might be a good solution to stick to only one language in stack.
Re:Our Machinery Guidebook by selfhoster11 on Wednesday July 06, 2022 @05:58AM (#31998802)
What's wrong with that?
Re:Our Machinery Guidebook by contingencies on Wednesday July 06, 2022 @10:32AM (#32001590)
String work in C for starters. Commonly accepted best practice is to use the least powerful language for any given problem. This is so it's (a) readable (b) portable (c) nominally secure (d) preserving of programmer time.

While there are exceptions, their reasons are questionable at best. It seems more like a declaration of a cultish C culture. Which, in context, is probably attractive to some of the people they're looking for, but hideously backward by general standards. Use the right tool for the job.

Re:Our Machinery Guidebook by pure-struggle on Wednesday July 06, 2022 @12:30AM (#31996726)
Yesh...