8 ms·
You need to patch Chromium on Linux to get hardware accelerated video playback. In addition, you need to either have a Skylake or later CPU or tell YouTube to s
by lern_too_spel 7y ago
You need to patch Chromium on Linux to get hardware accelerated video playback. In addition, you need to either have a Skylake or later CPU or tell YouTube to serve H.264 encoded video instead of VP9. This has nothing to do with web app vs. native.
- paxys 7y ago> This has nothing to do with web app vs. native Considering you don't have to do any of this on a native app (VLC) and just automatically get all the performance improvements, this has everything to do with web app vs. native
- pjmlp 7y agoActually it is more a consequence of Web browsers blacklisting your GPUs, even when they should be ok. This is why WebGL hasn't really taken off for gaming. You can have the perfect game running on 60 FPS on your system, then random dude tries to play the game, and browser decides it is blacklisted, goes back into software rendering and everything is choppy. Meanwhile he/she doesn't have any issue playing native games and wonders why the browser game doesn't cut it.
- de_watcher 7y agoMeh, the first thing about the browser games is the load time. It's not like downloading a native game and reliably storing it. The second thing were the CPU/memory problems because all the code was in js.
- vardump 7y agoOk, I'm very much pro-native for intensive applications, but... > Meh, the first thing about the browser games is the load time. It's not like downloading a native game and reliably storing it. What's the difference between native game on an SSD vs browser game on an SSD (web local storage)? (Ok, other than time taken compiling that js monster, unless webassembly is used.) > The second thing were the CPU/memory problems because all the code was in js. First of all, you can also use webassembly. Secondly, you can program js in ways that don't cause much memory bloat. Native arrays, etc. Especially when compiled from C/C++/Rust etc. Of course browser games have significant handicap. But I don't see any reason for them not to eventually reach at least 50% performance compared to native. Maybe even more. For a lot of applications, that's more than enough.