@pidotdev Thanks, the docs confused me with this part: "Radius does not currently guarantee a specific processing location..."
I just had a look , it seems like I'm unable to find it. (EU routing and ZDR would be huge for us )
Day 1 of testing Orbs: Love it so far. I'm still only scratching the surface, but it _feels_ very good.
Need to test how it'll work for major changes, but I see the potential. Also it feels magic when Orbs speak to Orbs. Great work! @thorstenball
It's so frustrating how clankers are still so bad at designing proper types and interfaces. Had to spend the whole day to clean up slop. It feels like there was no improvement since opus 4.x at all
Hi @thorstenball, I'm currently preparing my code to be able to work nicely in cloud envs and would love to try Orbs. I was wondering what do you guys recommend if the work involves multiple repos to complete a task. e.g: "change xyz in repo 1 after that change xyz in repo 2"
A post of ours on vendor lock in and LLMs. We don't like the growing trend of AI companies quietly hiding your data while stripping away your control. We think that's bad for users and bad for the ecosystem. Here's are our thoughts: https://t.co/pM4fBX0Z1T
@boristane If you use it right, the impact in performance can be neglected compared to what you gain from distributed observability across your systems
@zeeg I build everything on top of PI directly. Similar like Flue does, but focused on my needs.
The agents either use durable objects or full blown sandboxes (depending on what they need to do)