zlacker

[return to "Microsoft's Copilot chatbot is running into problems"]
1. pjmlp+Vi[view] [source] 2026-02-04 17:32:03
>>fortra+(OP)
It is remarkable how during the last 25 years (approximately), Microsoft has been improving their ability to deliver first (or be among the first), followed by messing up the whole process so that late comers end up taking the crown jewels.

PDAs, mobile phones, tablets, tablets with detachable keyboards, managed OS userspace, HoloLens, the XBox mess, and now AI.

There certainly other examples that I failed to address.

This is what happens when divisions fight among themselves for OKRs and whatever other goals.

◧◩
2. except+Yj[view] [source] 2026-02-04 17:35:22
>>pjmlp+Vi
And their philosophy of mediocre = good enough. (Not everything ofc, MS is a continent. .net core, language design etc is top-notch.)
◧◩◪
3. pjmlp+lm[view] [source] 2026-02-04 17:46:06
>>except+Yj
Which certainly has to do with it being initially developed at Microsoft Research Cambridge, and not plain Microsoft.

>>40472977

https://web.archive.org/web/20190111203733/https://blogs.msd...

◧◩◪◨
4. brg+Zn[view] [source] 2026-02-04 17:51:39
>>pjmlp+lm
I would argue that the success has more to do with DevDiv being the strongest technical organization at MS than its provenance.
◧◩◪◨⬒
5. pjmlp+qs[view] [source] 2026-02-04 18:09:27
>>brg+Zn
Until they messed up the whole UWP / WinRT developer experience in Visual Studio.

Also VS 2026 was released with a hard milestone, thus while there is a new settings experience, many options show a dialog from VS 2022, because the new UI is still not implemented for the new experience.

Note that most organisations have to pay for Visual Studio licenses, and get rewarded with such quality.

Slop has also arrived into DevDiv.

◧◩◪◨⬒⬓
6. PaulHo+NW[view] [source] 2026-02-04 20:28:41
>>pjmlp+qs
I think after the failure of Metro, I think Microsoft gave up on native apps entirely and now the story is web or Electron.
◧◩◪◨⬒⬓⬔
7. pjmlp+Q51[view] [source] 2026-02-04 21:06:43
>>PaulHo+NW
It appears the problem is more deep than that.

From what I could infer from some community talks, podcasts and so, I would assert that nowadays they have the problem new hires have been educated in UNIX like OSes and Web.

Thus Windows team gets lots of folks that never coded anything for Windows, and management instead of having proper trainings in place, just goes with Webview2 and Electron all over the place.

I might be wrong, this is more my perception than anything else.

◧◩◪◨⬒⬓⬔⧯
8. Mister+7u1[view] [source] 2026-02-04 23:13:51
>>pjmlp+Q51
I would say the web took over as the primary application platform and Unix-likes provided convenient low cost license-free foundations to build them on.
◧◩◪◨⬒⬓⬔⧯▣
9. pjmlp+Xp2[view] [source] 2026-02-05 07:43:22
>>Mister+7u1
No excuse for not having trainings in place for Windows native development, for those new hires.

You don't see Apple and Google doing the same Webviews all over the place on their OSes, with exception of ChromeOS, which appears to be on the death row to be replaced with Android anyway.

In fact, at WWDC 2025 Apple executives even spoke publicly on the matter against that approach.

[go to top]