> IAM can stay MS That's leaving the most critical component still with a US company.
> IAM can stay MS That's leaving the most critical component still with a US company. Doesn't fly if the goal is what the Danish agency is trying to achieve. > It actually depends how you use it. Obviously but the larger the company, the more ways to use it, and one of those ways will be a nightmare to tackle. You want one solution, not a patchwork. So the one that does everything gets picked. MS throws everything and the kitchen sink in their ecosystem to fit every need even if sometimes at mediocre or crappy quality. > For Teams, as long as you use it for conferencing and chat (no file sharing or editing), you can replace it with Slack Taken in isolation you're right. But in a world of network effects every company, supplier, service provider you work with might use Teams and you can federate. Switch to Slack alone and you make your life harder. I mentioned this in another comment, if protocols and formats were mandated to be open or interoperable (in practice) to allow usage in the public sector, replacing MS would be a notch or 2 simpler.
Posted by close04 on Feb 26, 2026, 10:56 AM
Tags
Related issues
- (1) Because it doesn't actually solve the problem.
- Every time fossil comes up, I hear this same issue - "why is there no rebase?" And honestly, I've never been able to get this argument.
- My biggest problem with running local LLMs on my M4 Max/128GB RAM is the prefill latency.
- Biggest problem with httpx I see is authors sanity https://github.com/encode/httpx/discussions/3784 .
- There aren't many situations today that make one think: Why doesn't this business have a website?
- I am very petty about this one bug and have a very old axe to grind that this reminded me of!
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
hackernews (Network)
(1) Because it doesn't actually solve the problem.
NewEvery time fossil comes up, I hear this same issue - "why is there no rebase?" And honestly, I've never been able to get this argument.
My biggest problem with running local LLMs on my M4 Max/128GB RAM is the prefill latency.
Biggest problem with httpx I see is authors sanity https://github.com/encode/httpx/discussions/3784 .
There aren't many situations today that make one think: Why doesn't this business have a website?
> IAM can stay MS That's leaving the most critical component still with a US company.
I am very petty about this one bug and have a very old axe to grind that this reminded me of!
Not just the edge router.
> IAM can stay MS That's leaving the most critical component still with a US company.
> IAM can stay MS That's leaving the most critical component still with a US company. Doesn't fly if the goal is what the Danish agency is trying to achieve. > It actually depends how you use it. Obviously but the larger the company, the more ways to use it, and one of those ways will be a nightmare to tackle. You want one solution, not a patchwork. So the one that does everything gets picked. MS throws everything and the kitchen sink in their ecosystem to fit every need even if sometimes at mediocre or crappy quality. > For Teams, as long as you use it for conferencing and chat (no file sharing or editing), you can replace it with Slack Taken in isolation you're right. But in a world of network effects every company, supplier, service provider you work with might use Teams and you can federate. Switch to Slack alone and you make your life harder. I mentioned this in another comment, if protocols and formats were mandated to be open or interoperable (in practice) to allow usage in the public sector, replacing MS would be a notch or 2 simpler.
Comments (0)
No comments yet. Start the discussion.