171–180 of 193 posts
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.
mpv is that. In 2010 mplayer2 forked from mplayer, in 2012 mpv forked from mplayer2. It's all I've used since.
Earlier quoted context omitted.
It stopped being a thing about 10 years ago. Mostly because everything is H.264, H.265, VP9, AV1, MP3 or AAC.
So the weekly updates are... fake? https://codecguide.com/changelogs_standard.htm
https://blog.jquery.com/2026/01/17/jquery-4-0-0/
And so is COBOL.
https://docs.rocketsoftware.com/bundle/visualcobol_rn9_90_pd...
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.
It's come and gone, and I'm still not fully sure what Groove Music was; was it something to do with the Zune?
Earlier quoted context omitted.
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.
A single Chrome tab does not use gigabytes. In fact, this app IS a Chrome tab! It's web based, so it's using Edge, which is just Chrome in a trenchcoat.
Earlier quoted context omitted.
'It's worse for our users, but easier for our developers' is an unacceptable tradeoff, they deserve the backlash.
'It's worse for our users, but easier for our developers' That's how a lot of software gets done these days. More bloat, less features, lots of inconsistencies.
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.
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…
'It's worse for our users, but easier for our developers' is an unacceptable tradeoff, they deserve the backlash.
The programs shipped with the OS should be exemplary versions of each thing.
I rarely use widows, but i feel like windows media player is only there to check a box that windows has a media player. Most people dont play local videos anyway, and those who do use something else like VLC.
feel like windows media player is only there to check a box that windows has a media player
Earlier quoted context omitted.
Well there's an old kid in town, MPC-HC is still being maintained[1] to the great joy for us who dislike the VLC UX. [1]: https://github.com/clsid2/mpc-hc/
If mpv on Linux and MPC-HC on Windows, what is recommended on macOS?