danbee

Yes, it does. It always renders internally at 2x which means that's all applications have to support. Then it downsamples the final framebuffer to the resolution of the display.

There is zero point in sampling higher than 48khz. That captures all frequencies up to 20khz or so. 192khz is just a waste of bandwidth for no actual gain.

For years my iPhone would try to autocorrect "mum" to "nun".

We already have a markup language capable of this. It's called HTML.

On the flip side I built a PC back in 2016 (with two SSD's) which went into storage about 6 months later. I just got that PC back this year and it booted up just fine with all the data intact.

I'm not a fan of Prettier at all. A log of the time I find it makes code uglier.

At the time Apple Maps came out, Google Maps on iOS was limited to bitmap tiles and had no turn by turn directions, whereas Google Maps on Android had both dynamic vector based maps and turn by turn directions.

Apple Maps forced Google to improve Google Maps on iOS.

Apple Maps data was definitely substandard when it was released, but it has improved considerably since then. I vastly prefer it to Google Maps, especially for turn by turn directions when I'm driving.

The Switch is 1280x720 and the Steam Deck is 1280x800. They're not the same size.

FLAC has a massive advantage over WAV/AIF in that it can be tagged with metadata for the music player software to read and display.

48Khz can theoretically be better because the anti-aliasing and reconstruction filters can have a gentler slope, but modern oversampling converters make this moot now.

Decibels is a logarithmic (and relative) unit, not linear. So each bit represents 6db or a doubling of amplitude.

The audio jack on Raspberry Pi's has always been terrible quality anyway. Ok in a pinch but it's not a huge loss. If you want quality analog output from a Pi you need a DAC hat.

You won't have to. They can all be stacked.