←back to thread

336 points mohi-kalantari | 1 comments | | HN request time: 0.195s | source
Show context
kayhantolga ◴[] No.46195479[source]
As a .NET developer who actually likes some Microsoft products, I can say this: the Copilot series is the worst thing they've shipped since Internet Explorer—and honestly, it might overtake it. The sad part is they had a huge head start before competitors gained access to powerful models, yet this is what we got.

If you haven’t seen how bad it is, here’s one example: Copilot Terminal. In theory, it should help you with terminal commands. Sounds great. In practice, it installs a chat panel on the right side of your terminal that has zero integration with the terminal itself. It can’t read what’s written, it can’t send commands, it has no context, and the model response time is awful. What’s the point of a “terminal assistant” that can’t actually assist the terminal?

This lack of real integration is basically the core design of most Copilot products. If you’ve been lucky enough to avoid them, good for you. If your company forces you to use them because they’re bundled with a Microsoft license, I genuinely feel your pain.

replies(8): >>46196100 #>>46196148 #>>46196271 #>>46196343 #>>46196418 #>>46196569 #>>46196754 #>>46197123 #
1. adabyron ◴[] No.46196271[source]
When was the last time Microsoft had a unified vision that was focused on building an amazing line of products that integrated well with each other?

I can only think of short snippets in history where they moved in that direction for maybe a year or two & then went scatterbrain.

Microsoft has benefited from a monopoly in the enterprise and has never been forced to innovate from a product perspective. See Slack/Teams as a case study of how they have operated when even slightly pushed.

* Edit - .NET, C#, TypeScript teams are an exception to the above. Highly underrated. Amazing talent there. Not sure who all gets credit. Anders & Mads for sure though.