Hacker News Reader

Comment by jjcm | Hacker News Reader

I think what I find fascinating about this is it's a native app with no web version... and they still decided to write it in html/js. This is after Microsoft's commitment to rebuild things in WinUI.

Don't get me wrong, I totally understand the barrier of friction that native presents compared to html/js, but that barrier has lowered so much with the advent of agentic development. It just feels like things weren't thought out.

View on HN

1. It does not use HTML/JS. It is a fully "native" app (at least if C# counts as native) written with C# and UWP/WinUI2 XAML. Actually, Xbox Music in Windows 8.x had a web tech based UI; when it was rebranded as Groove Music in Windows 10, its UI layer was rewritten. Xbox Music itself in turn was a reskin/rewrite of the UI layer of Zune (which was C++) so it's already been through full cycle of native->web->native. (The "new" Media Player still identifies as "ZuneMusic" in packaging metadata!)

2. it's not "after"; Groove Music was largely written in 2014-2017 in the early Windows 10 days, and even its rebrand as Media Player in Windows 11 happened in 2022, and it's barely been touched since then.

> at least if C# counts as native

It can count as native. You can turn on Native AOT compilation:

https://learn.microsoft.com/en-us/dotnet/core/deploying/nati...

There isn't even really a barrier. It's not actually hard to do UIs in WinForms, nor WPF, and I assume not in WinUI either. The problem is that a lot of people are just too lazy to even try to step out of the HTML/JS comfort zone, not that it's hard to do.

Which barrier?

Reply on news.ycombinator.com