Yah it does. I’ve got 2 4K’s and only 1 supports HDR and I’ve never had a problem with it.

I do occasionally have weirdness where HDR or the framerate don’t get detected right though and I have to unplug and replug the HDMI cable

Yes, it works. When you’re in a video there’s a ^ in the top right corner that’s got settings for captions and a few other things. Also under the apps settings you can toggle it to use the Android OS captions system that has more options for contrast and font size

I don’t think it’s a far fetched statement, but I’m also not sure if it’s true.

I know concrete has a pretty big carbon footprint, but, I don’t know how that scales in relation to the carbon savings of nuclear power.

Oh for sure, but it’ll be easier to cable manage if it’s closer to the edge of the board like over by the 24-pin or something, which is probably the real W with this standard.

The party of compromise has been working hard to find middle ground and bipartisan support from people who dog whistle to neo nazis. It doesn’t surprise me to hear someone eyeballing the 3rd party route.

Not that I think you’re wrong about the math and who will ultimately win if it becomes a serious thing, I’m just not surprised people are getting heated and stoking some fires.

Now

Not surprising tbh, loads of mid-range Android phones do that. They’ll implement USB4 in a year or 2 and maybe be the first to implement it in a phone, then talk the biggest game about it at their developer conference like they invented USB or something.

It’s pretty cyclical at this point, they’re saving a talking point for later

I originally had words about ahead of time compilers like GraalVM but got tired of looking at my own wall of text so I trimmed it down and left compiler to mean ahead of time compulers, which I see caused confusion, you’re right on those points.

I know the JVM hardware exists also, but, it’s specialty hardware even at the enterprise level. You could technically make an ASIC that executes QBASIC at hardware but I’m not sure I’d believe that makes it a compiled language since it would be neither wide spread nor the original use case for it. That’s kind of a philosophical argument though

I think my use of compilers in interpretation may also be confusing, interpreters have an execution step, which at some point translates to a machine representation of your code. It’s referred to as execution, but, it feels a lot like a compile+execute step

I think you’re missing that all interpreters have a compilation step that produces machine code, that’s a requirement to produce programs.

Java’s JIT compiler is the final compilation step of Java’s interpreting path running in a separate thread that turns the intermediate language to machine code. To be very clear though, the output of the standard javac compiler is not machine code that a processor understands. This is what makes Java not a compiled language. It depends on additional processes at runtime to turn the code you wrote into something a processor understands.

On the performance front, well written Java is fast enough as long as you have sufficient resources for the overhead of JVM and as long as you don’t have strict latency requirements. That makes it good for a pretty wide variety of computing tasks, but, also not a good choice for a lot of others.