News for hackers. Stuff that matters.
Re:Windows 11 New Media Player Uses 3.5x More RAM, Charges f... by VladVladikoff on Saturday June 20, 2026 @02:38PM (#48611733)
>As for the RAM increase, well that's probably a consequence of the general trend of doing frontend engineering via JS/TS instead of using OS native frontend APIs

Can someone explain to me why these multi operating system app building tools don’t compile down to native code and leverage native APIs? Is there nothing like that available?

Re:Windows 11 New Media Player Uses 3.5x More RAM, Charges f... by AlotOfReading on Saturday June 20, 2026 @03:09PM (#48612017)
Microsoft has written more application development frameworks than you can shake a stick at. They've also failed to gain traction with virtually all of them, even internally.
Re:Windows 11 New Media Player Uses 3.5x More RAM, Charges f... by contextfree on Saturday June 20, 2026 @11:22PM (#48615374)
WinUI2/UWP was heavily adopted internally though?* Most Windows shell UI and built-in apps use it at this point.

* (at least within the Windows organization; maybe not so much in other parts of Microsoft)

Re:Windows 11 New Media Player Uses 3.5x More RAM, Charges f... by happymellon on Sunday June 21, 2026 @03:48AM (#48616617)
Leadership is weak.

As an operating system vendor, it should be a dismissable offence to refuse to use the OS standard APIs. Your products need to be the standard that other try to imitate.

Re:Windows 11 New Media Player Uses 3.5x More RAM, Charges f... by mfro on Saturday June 20, 2026 @04:28PM (#48612695)
The web browser is a compiled program. The problem is that it’s a huge program.