I haven't looked into the details of the actual code, but I would expect the compiler optimizations and JIT to figure it all out and end up with very similar native code. Especially since both languages are mature and had enough time to reach such goals. But it's quite possible my assumptions are incorrect.
I upgrade as soon as new versions come out, I like living on the edge :) if something goes wrong, there are backups.
As for musl, I haven't mentioned it since OP wants to run containers - and in that case, musl doesn't matter. And for running programs natively, many are available as packages (with any musl incompatibilities already resolved). But yeah, if you venture outside these limits, you can definitely run into issues with musl.
I've tried twice to listen to it so far, but no luck. I am planning to try again, though. I got further on the 2nd attempt.
Ah. Sarcasm is difficult to see in text based communication.
Not sure what Linux ISOs are, but it's pretty rare that something is only available with Dolby Vision and not HDR10. Have you verified that HDR10 gives you trouble? 4K HDR is also usually HDR10, unless specifically marked as DV, in my experience.
Anyway, another option, if you don't care for HDR, is to transcode/tonemap everything in the background. This way, you don't have to worry about performance during playback.
Android TV should handle HDR automatically (and tonemap it if needed).
Green and pink tint sounds like the source is Dolby Vision, not HDR10. So, 2 questions:
- Why do you need HDR sources if your displays don't support HDR?
- Assuming the answer to (1) is that you're future-proofing, why not just get HDR10 files instead of Dolby Vision?
Hear me out. Why don't we create a paywalled API for 3rd party apps (like Threads), that will end up costing, say, $20 million annually to use at Meta's rate... And then use the proceeds to keep all the instances running, and for other shenanigan.
Try punching 2 holes in your tire, and demand to pay for at most 1 puncture repair, let's see how far that 0 or 1 hole argument gets you :)
Depends what you’re transcoding to… show me a CPU (without a built in encoder like recent ones) that can handle a 4K HDR transcode…
What about kbin?
Is this about the PWA rotating when auto rotation is set to off? Sounds like a bug on the device, as it's not happening to me.
Maybe when IPv6 is widely available, we'll stop seeing this... For now, it sucks, but IPv4 blocks are expensive. Price or external IPv4, something's gotta give.