hchja

MCP was much more important when agents weren’t able to accurately make tool calls.

Nowadays, these agents are more capable and I think you can replace MCP (which is a pain on macOS), with simple CLI tools and expose them to agents via system prompt, skills, or other API documentation.

The fact that it doesn’t explain its reasoning at all (there is no way to make it do so), makes me question the utility of this model.

Let’s say you deploy it in production and a user comes back and says “Why is this prompt considered harmful?”

You have no way to provide a concrete reason to the user at that point.

Why would you want/need change when it comes to OS of choice in the public administration?

If you personally prefer Linux then you should install that. Maybe I’m not understanding the impact of one over the other in this scenario or if it’s a long historical gripe thats shared between many Munich citizens?

This is pretty useless in any case that doesn’t involve BFloat16 models

This is why language syntax is so important.

Swift allows a ‘default’ enum case which is similar to other but you should use it with caution.

It’s better to not use it unless you’re 110% sure that there will not be additional enums added in the future.

Otherwise, in Swift when you add an additional enum case, the code where you use the enum will not work unless you handle each enum occurrence at it’s respective call site.