61–70 of 193 posts
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.
Removing HEVC support wasn't their choice but probably stems from the licensing pools increasing their prices [1]. Windows media player probably sees very little usage nowadays and probably even less for HEVC, when most content playback happens via streaming and browsers today. 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…
Earlier quoted context omitted.
'It's worse for our users, but easier for our developers' is an unacceptable tradeoff, they deserve the backlash.
I mean... Yes, but there's nuance here. Using 400 MB of RAM vs 100 MB of RAM is close to unnoticeable in a world of a GB+ for a single Chrome tab ... And if "easier for our developers" means the end user is getting more regular updates with fewer critical issues, then it's not an uncomplicated tradeoff at all, parts of it are actually synergistic.
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 tho…
Removing HEVC support wasn't their choice but probably stems from the licensing pools increasing their prices [1]. Windows media player probably sees very little usage nowadays and probably even less for HEVC, when most content playback happens via streaming and browsers today. 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…
Removing HEVC support wasn't their choice but probably stems from the licensing pools increasing their prices [1]. Windows media player probably sees very little usage nowadays and probably even less for HEVC, when most content playback happens via streaming and browsers today. 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…
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?
Removing HEVC support wasn't their choice but probably stems from the licensing pools increasing their prices [1]. Windows media player probably sees very little usage nowadays and probably even less for HEVC, when most content playback happens via streaming and browsers today. 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…
Windows 11 is not free software. Apple macOS, iOS, ipadOS all support HEVC and Dolby because Apple pays licensing costs, likewise Microsoft should do the same for Windows users, it is not free OS.
Removing HEVC support wasn't their choice but probably stems from the licensing pools increasing their prices [1]. Windows media player probably sees very little usage nowadays and probably even less for HEVC, when most content playback happens via streaming and browsers today. 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…
ms-windows-store://pdp?productId=9N4WGH0Z6VHQ
It's a wide know workaround, been there for years, obviously Microsoft pretends they don't know about it.
https://www.howtogeek.com/680690/how-to-install-free-hevc-co...