Last update seems to be from 2022 at mplayerhq.hu.
Used to be the go-to that played basically anything years ago.
101–110 of 193 posts
Last update seems to be from 2022 at mplayerhq.hu.
Used to be the go-to that played basically anything years ago.
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…
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.
Earlier 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.
> The modern Media Player is said to use around 377MB of RAM when idle, compared to roughly 103MB for the old player—about 3.5x as much memory while doing absolutely nothing. even 103MB sound like a lot for doing nothing
We might expect newer players to cache less because SSDs are fast, but perhaps this is offset by the increasing use of network storage, whether it’s internet-based or a local HDD NAS.
Windows core apps used to be pure C++.
Cry long enough about "safe" languages and expect to take the RAM hit.
Earlier quoted context omitted.
It does not matter how well or poorly Chrome mismanages memory, 400MB is still 400MB. If that 400MB is 10% of the free RAM after the share the OS takes, then that is a hefty toll. And the regular updates Windows 11 users are getting are famously not providing value, but taking value away. Case in point right here is the new media player.
People try to use Windows 11 with 4GB of RAM? I doubt that's viable, honestly... At that point, just don't use microslop software
#StopTheBloat #StopTheOffshoring
Hmm anyone remembers mplayer? Last update seems to be from 2022 at mplayerhq.hu. Used to be the go-to that played basically anything years ago.
Earlier quoted context omitted.
No, no and no. Last year I paid money to upgrade my laptop's RAM from 16 to 32 GB. I didn't pay it so apps could just be more bloated without offering any significant benefit. Developers should respect and be efficient using hardware resources. There are no excuses for that.
From CS101 it’s called virtual memory. Things get swapped in and out of memory when they need to. An extra 200MB of memory when Chrome takes gigabytes of memory is a petty thing to complain about. How much do you want to bet you don’t even use windows media player? It’s fake outrage and if you care that much use VLC.
Great, so now that SSD I've got can wear out more quickly!
> It’s fake outrage and if you care that much use VLC.
Already do. My heart still aches for those who don't know any better.
Earlier quoted context omitted.
It does not matter how well or poorly Chrome mismanages memory, 400MB is still 400MB. If that 400MB is 10% of the free RAM after the share the OS takes, then that is a hefty toll. And the regular updates Windows 11 users are getting are famously not providing value, but taking value away. Case in point right here is the new media player.
People try to use Windows 11 with 4GB of RAM? I doubt that's viable, honestly... At that point, just don't use microslop software