Live data from Hacker News

Microsoft Agent Framework

learn.microsoft.com

11–20 of 32 posts

Re: Microsoft Agent Framework

#14
post #3

Curious what people see in these frameworks in 202(6). My experience has been that an agent is a simple while loop over tools/instructions/dialog. More complex integrations generally lie in the tools/context retrieval - but those have so far been so domain specific that it’s not worth pulling in a framework.

Anything beyond this is usually a play to trap you into an ecosystem. No reason to adopt any of these frameworks, especially if you already have a mature workflow system.

Re: Microsoft Agent Framework

#15
post #10

I remember when "Microsoft Agent" meant the APIs that gave rise to Clippy, Rover, and (regrettably) even Bonzi Buddy. The bitter irony is, Microsoft has since embrace-extend-extinguished Bonzi Buddy spyware tech, building it right into Windows 11. So... they're moving onward to the future I guess?

> I remember when "Microsoft Agent" meant the APIs that gave rise to Clippy, Rover, and (regrettably) even Bonzi Buddy.

I remember Microsoft Agents as the enforcement arm of the Business Software Association.

They'd perform copyright raids on small biz, typically after some disgruntled employee phoned in an infringement tip.

Re: Microsoft Agent Framework

#16
post #8

Why throw in .net in the mix? That alone could squish all interest.

What’s the issue with net? It’s a modern cross platform open source language with very good performance

One of my grips with C#, Java,... is pushing runtime logic inside the type system. This leads to a huge standard library where there are multiple classes that are barely different than other other than implementation details.

I prefer Go's approach on preferring interfaces instead of inheritance. But what I like is Clojure and Lisp where the semantics of algorithms and data structure is not so diffuse.

Re: Microsoft Agent Framework

#18
post #10

I remember when "Microsoft Agent" meant the APIs that gave rise to Clippy, Rover, and (regrettably) even Bonzi Buddy. The bitter irony is, Microsoft has since embrace-extend-extinguished Bonzi Buddy spyware tech, building it right into Windows 11. So... they're moving onward to the future I guess?

I've toyed with the idea of hooking up something like Copilot to Clippy to make an "agent" using the Microsoft Agents API.

Unfortunately, the API died in Windows Vista, and was only widely available in Windows XP at the latest.

API documentation seems rather sparse too, though it looks like an LLM somewhere found a pirated book or something with example code because generated code seems to understand the API and its restrictions decently well. Writing the kind of C++ that still compiles on old versions of Windows is what broke my will to finish the project, though.

Re: Microsoft Agent Framework

#19
post #3

Curious what people see in these frameworks in 202(6). My experience has been that an agent is a simple while loop over tools/instructions/dialog. More complex integrations generally lie in the tools/context retrieval - but those have so far been so domain specific that it’s not worth pulling in a framework.

[dead]
Post reply on HN