Description
This story is sooooo confusing & frustrating... please help me understand this.
I'm asking this on behalf of a LOT of developers who are looking for guidance. What follows are some raw comments, but this is what I'm hearing from my customers (100's of Teams developers I've taught over the last few years). I understand their frustration and am trying to better understand your direction/position.
Why ANOTHER SDK & toolkit for creating Teams apps when there's already one (TTK/ATK) with an established user base?
As a long-time Teams developer, I don't get what this team is doing. Teams AI Lib v1... makes sense... totally. But an SDK when there's already an SDK for building Teams apps (TTK/ATK)?
This new direction with v2 & an SDK puts you at direct odds with the Agents Toolkit (ATK, formerly TTK). Side by side, they both have command line tools, packages, and project templates. But the ATK has a lot more support for environments, additional project types, debugging, etc. From the outside and from what I've seen in all the sessions at Build, I can't shake the impression that the group working on Teams AI Library has gone rogue.
In fact, the comment in your docs comes across as being very defensive & combative with the ATK group
Why would I use the v2 of your library to create a project for a tab?
I wouldn't... I'd only want to use your library to facilitate interaction between my code & LLM, exactly what I had before with v1.
Why does this library have its own MSGraph JS client?
Why not use the JS client from the official Microsoft Graph team that's always going to be more current & supported by the MS Graph team?
Sure, the improvement to support MCP is a big deal, but why not just have the library leverage what's there for the Agents SDK to do the same thing? Frankly, that should be baked into the Agents SDK.
I can't see why I'd take a dependency JUST to get MCP support in v2.
🙏 Please help me understand this story... it's just confusing & frustrating and hard to explain big picture to customers.