This is interesting — I’ve run into that exact pain point of spending more time on plumbing than building features.
Curious about the choice of C++ for the core runtime. Was the main driver raw performance, or more about portability and low overhead in production environments? In my case, I’ve mostly worked with Python pipelines and they tend to choke when you try to scale concurrency without overcomplicating the architecture.
The graph-based approach reminds me a bit of Unreal’s Blueprints, but for AI ops. If you can make it genuinely easy to plug in custom nodes without touching glue code, that could be a big productivity boost.
So... The true story is that it all started as an internal infra.
Originally, Inworld was mostly involved into gaming (read as Unreal & Unity) and therefore the choice. Yet (surprise, surprise) we want native x-platform and on-device (whose official support is coming soon).
Also, not a new thing, but C++ is more reliable than Python under really high concurrency, which was critical for us (a lot of people using same graphs in parallel kind of use case).
This is interesting — I’ve run into that exact pain point of spending more time on plumbing than building features.
Curious about the choice of C++ for the core runtime. Was the main driver raw performance, or more about portability and low overhead in production environments? In my case, I’ve mostly worked with Python pipelines and they tend to choke when you try to scale concurrency without overcomplicating the architecture.
The graph-based approach reminds me a bit of Unreal’s Blueprints, but for AI ops. If you can make it genuinely easy to plug in custom nodes without touching glue code, that could be a big productivity boost.
So... The true story is that it all started as an internal infra.
Originally, Inworld was mostly involved into gaming (read as Unreal & Unity) and therefore the choice. Yet (surprise, surprise) we want native x-platform and on-device (whose official support is coming soon).
Also, not a new thing, but C++ is more reliable than Python under really high concurrency, which was critical for us (a lot of people using same graphs in parallel kind of use case).