91–100 of 114 posts
Oh 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.
Reminds 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…
Pretty sure there are DDS implementations that provide most of that, maybe with memory pools instead of no-allocations. Other than that, PX4 uses an in-memory only pub/sub for internal data bus, somewhat inspired by DDS
But yes - there absolutely are solutions already. I guess I was just lamenting that they weren't really functionally accessible for all applications.
Earlier quoted context omitted.
There's a standard that has OMG as the acronym? OMG. I'm not even going to bother to search for that!
Object Management Group I think. Better known as the inventors of UML.
Corba never died!!! OMG!!
Who cares if german company wants to use this mess for their weapons.
I wonder if someone just got super annoyed at having to ask legal to share their documentation with a cooperation partner for export control clearance, that they decided getting it open sourced would be less of a hassle. Now they can freely link anyone to the document.
That'll be $1000 consulting fee on ITAR compliance.
“Hi Codex, please find attached website about the specification of my Battlesuit and use the documented API to create a plugin for Home Assistant that shows groups of sensor data. You are only allowed to use commands that retrieve data, you are not allowed to perform actions on the suit. Treat the suit like its API is not robust and in worse shape than a cheap toy: perform read calls slowly and sequentially with at l…
"The Kampfanzugskode isn't working well." - "Why can't we use KI to improve it? I've heard from Hans that this Klaus Kode is good at Programmierung." - "We can only use Mistral because of Regulierungen." - "Let's open source it then, so others can use Klaus Kode." - "Ja! This is indeed a legit Schlupfloch and a fantastische Idee!"
Reminds 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…
Zenoh ( https://zenoh.io/ ) is a good alternative to DDS in many cases - it scales down to microcontrollers with most features still intact, but scales up to a routed hybrid mesh if needed. It does move the schema enforcement out of the middleware layer, so it’s a bit different. But it’s now a first-class alternative middleware implementation for ROS2 as an alternative to DDS.