Interesting that its HDMI is 2.0 and not 2.1. Hopefully it's still possible (for those that really want) to connect modern 4K TVs at 120 hz via the DisplayPort 1.4 output.
Seems like a case of under promising and planning to over deliver later. The hardware seems to be 2.1 but they haven't sorted out every feature in the drivers yet.
> [...] the only reason to use gamma encoding for digital images is because it allows us to store images more efficiently on a limited bit-length [...]
It's interesting how this part of the trade-off changes when using float16 for color components (as is common when HDR is involved) rather uint8.
Good timing that Safari 27 adds support for srgb-linear and display-p3-linear color spaces.
I'm using it ocassionally - whenever I have time to do further WebXR development beyond what I've already done, and when an interesting new immersive video or 3D movie becomes available on it. I'll sometimes use it to relax and catch up on any new VR180 videos on youtube.
For other work or entertainment that doesn't take advantage of its spatial features, I tend to revert to using a computer with an external display. The display in the Vision Pro cannot quite match the resolution and HDR headroom of the external display I ended up having (a Pro Display XDR). Maybe if it didn't get outclassed by my external display when displaying 2D content, I'd have additional motivation to use it more often.
I am at Google, but that's probably not relevant since the reason I was curious about this is that my personal website currently implements a git server over HTTPS[1], and git's CLI/API for that is not the friendliest[2]. It sounds like jj hasn't reached the point of tackling this problem space yet, which is okay. Thanks for confirming I wasn't missing out on something.
More infrastructure than content, but in principle it’s capable of hosting Go packages, complete with a simple issue tracker and code review system. I use it myself to stream notifications from multiple sources (GitHub and Gerrit).
