Oh boy, just what the world needs right now. Open source weapons APIs!
MAVLink has been open source for over a dozen years and with better tooling and apis.
German Rheinmetall open-sources its Battlesuite connected weapon system protcol
81–90 of 114 posts
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#82Open the C++ example up and the first thing I see: ```cpp std::cout Generally, I've heard `std::endl` instead of \n has bad performance because it forces the statement to print immediately. And because cout is guaranteed to flush anyways when the program ends, you're adding a delay for no reason. I wonder if there's something I'm not seeing that led to them adopting this rule. e.g. "abnormal program termination" caus…
This seems like an incredibly unimportant quibble... I would imagine they just used std::endl b/c that's what most random tutorials used in the 2000s and that's how the engineer learned. If you are printing a debug string, you probably don't care that much about perf in the first place.
Ask yourself, would a newbie make that mistake ?
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#83Nah, they haven't open sourced anything: https://github.com/rheinmetall . They just published the documentation. Really weird, what's the point?
Theres probably some tender that says it must be a "open platform" "open ecosystem" "modular vendor independent" whatever. So you upload some slop to GitHub and tick the box.
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#84[flagged]
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#85Earlier quoted context omitted.
I'm gonna steal "Klaus Kode", that one really got me.
I sense you'd enjoy the signup process for Klaus Programmieren: https://klausprogrammieren.com/
oh my god, that's gotta be the best European innovation I've ever seen in a long time
this deserves an EU grant
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#86Reminds me a lot of the Tactical Microgrid Standard (aka TMS aka MIL-STD-3071) [1], probably just because TMS uses DDS as well. I would really like to know if there is a protocol that functions like DDS but caters to real-time guarantees and prioritizes (at a "simple protocol" level) usability on embedded systems with no dynamic memory allocation. It would also need to be just-as-functional with non-real-time systems…
TIL there are people using DDS for non-realtime
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#87Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#88Oh boy, just what the world needs right now. Open source weapons APIs!
MCP is 100% already in the works.
> Claude, please execute the insurgents. Make no mistakes.
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#89Sounds like the Land Data Model (LDM) of the Generic Vehicle Architecture (GVA) [1] that the UK MOD has. GVA is closed source however.
[1] https://en.wikipedia.org/wiki/Generic_Vehicle_Architecture
Re: German Rheinmetall open-sources its Battlesuite connected weapon system protcol
#90Open the C++ example up and the first thing I see: ```cpp std::cout Generally, I've heard `std::endl` instead of \n has bad performance because it forces the statement to print immediately. And because cout is guaranteed to flush anyways when the program ends, you're adding a delay for no reason. I wonder if there's something I'm not seeing that led to them adopting this rule. e.g. "abnormal program termination" caus…
> cout is guaranteed to flush anyways when the program ends
This is not always true in the case the program crashes. I've had case where `std::endl` was necessary.