Windows 11 New Media Player Uses 3.5x More RAM, Charges for Popular Video Codecs
121–130 of 193 posts
Re: Windows 11 New Media Player Uses 3.5x More RAM, Charges for Popular Video Codecs
#122Earlier quoted context omitted.
'It's worse for our users, but easier for our developers' is an unacceptable tradeoff, they deserve the backlash.
Very few users care about how much RAM their media player uses. The practical difference between 370MB and 100MB is basically nil for any normal workload. It affects nothing but how many unlikely-to-be-used files fit in the page cache.
Re: Windows 11 New Media Player Uses 3.5x More RAM, Charges for Popular Video Codecs
#123For everything except sabotage-ware rootkit based games, Linux is the better solution for basically everything. Running MS Windows these days is like having a "kick me, hard" sign on your back. Or, you're treated like a money and data piñata.
There is a lot of professional software that locks people in also.
Re: Windows 11 New Media Player Uses 3.5x More RAM, Charges for Popular Video Codecs
#124Earlier quoted context omitted.
I don’t recall ever having a good time using a native Mac OS video player.
QuickTime is fine. It does the basics, is intuitive, and fast.
Re: Windows 11 New Media Player Uses 3.5x More RAM, Charges for Popular Video Codecs
#125Removing 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…
How do we live in a world where simultaneously "human coding is dead" and also "we need to trade performance for developer efficiency"? I thought code is free now?
Also--this is Microsoft! It's their OS!
Microsoft should just come out and say that the whole of Win32 is deprecated and kept around for legacy compatibility only, and all new software should be written in Electron. They're already acting that way, why not make it official?
Re: Windows 11 New Media Player Uses 3.5x More RAM, Charges for Popular Video Codecs
#126The suffering will continue until there are good alternatives.
Re: Windows 11 New Media Player Uses 3.5x More RAM, Charges for Popular Video Codecs
#127Earlier quoted context omitted.
Very few users care about how much RAM their media player uses. The practical difference between 370MB and 100MB is basically nil for any normal workload. It affects nothing but how many unlikely-to-be-used files fit in the page cache.
Have you heard that there's a RAM shortage?
Re: Windows 11 New Media Player Uses 3.5x More RAM, Charges for Popular Video Codecs
#128Well it's written in managed code, what do you expect? Windows core apps used to be pure C++. Cry long enough about "safe" languages and expect to take the RAM hit.
WinUI, WinAppSDK are built on top of WinRT, which is C++ for the most part. That is the whole joke about it, Windows division tried to kill .NET with their updated COM based on Vista victory over Longhorn, and the whole AddRef/Release makes it slower than WPF applications. https://arstechnica.com/features/2012/10/windows-8-and-winrt...
Re: Windows 11 New Media Player Uses 3.5x More RAM, Charges for Popular Video Codecs
#129Earlier quoted context omitted.
Have you heard that there's a RAM shortage?
Do you have telemetry about how often systems are overcommitted due to Windows Media Player memory usage? I'll bet Microsoft does.
Re: Windows 11 New Media Player Uses 3.5x More RAM, Charges for Popular Video Codecs
#130Earlier quoted context omitted.
Have you heard that there's a RAM shortage?
Do you have telemetry about how often systems are overcommitted due to Windows Media Player memory usage? I'll bet Microsoft does.
Considering the way Microsoft's product line is these days, I have a hard time believing its terabytes of "telemetry" go anywhere but the Windows equivalent of /dev/null.