I 100% believe it's Windows' fault on this one.

I've never had problems with VLC in over a decade of use until MS started vibe coding everything and doing zero QA.

“Bug”

VLC does so much more than play videos, but honestly, the interface is bonkers.

The one thing they've refused to do saying it's too hard, or whatever, is backward frame-by-frame stepping. SMPlayer has done it for as long as VLC has refused to do it. Celluloid does it, too.

I've been using MPC-QT for a while on Linux after deciding to ditch VLC. It works pretty well.

If I end up with a weird file I can't open or something, I'm glad the VLC tool is there if I need it. But as an everyday media player, I found the experience to be lacking.

I always wondered if it was just my pc that was painfully slow opening VLC.

I end up with issues with it because I do a lot of graphic design which means I have a lot of fonts. So, it ends up rebuilding its subtitle font cache for little reason every time I start it. Can at least disable that though.

I installed a local Jellyfin server pointed to my media, and just connect to 127.0.0.1:8096 in the browser or app. Jellyfin is a crazy good media player.

But as the article says, it works awfully slow on windows 10 as well, I thought it was just me.

I read the article. The author questioned why this bug has existed for so long, and if it’s also a design flaw of vlc.

Ways of stating the obvious