752 karma · joined August 22, 2017
Sometimes you need to look at two–three windows at a time. Maybe four (a terminal) that can live sort of to the side of the main two–three windows. A scrolling VM lets you work more fluidly instead of forcing everything into a screen-sized box. It’s useful to have a note-taking app side-by-side with a document you work with or a webpage for research. (Not all apps are designed to be used fullscreen. E.g. a calculator.)
https://www.theregister.com/2021/11/11/latest_windows_11_bui...
This is probably it.
HTTP Client Hints spec can send the viewport size and pixel ratio and even a low-bandwidth preference as HTTP request headers. It’s only supported in Chrome and requires extra round trips. The other browser vendors have been unwilling to implement the spec.
You’ll love what they’ve done in Windows 11.
But then you still want to serve a small video file (320px wide) for mobile and a larger one for desktop (600px wide).
> While it would be possible to have the ability to select different video sizes/quality rates based on HTML elements and attributes, it is likely impractical to handle, say, adaptive video streaming (where the quality of the video is based on the connection), purely in HTML.
Adaptive streaming where the quality changes over time as you watch is only needed for longer videos. You don’t need that for a short one minute video or a GIF equivalent. Just picking a resolution appropriate to the screen size would be enough.
It may work, but … ugh. This is a spec issue.
Anyhow: the point was that it’s too difficult to embed videos even if you’re willing to bear the hosting cost.
It costs roughly 0.0015 USD per hour video in 480p/VP9 hosted with BunnyCDN. The cost is manageable.
Everyone hangs out on Daily Motion, Vimeo, Cinnamon, D.Tube, and PeerTube all the time. Right?
It can, yes. The response header `Accept-CH: Viewport-Width` suggest to the client that future request should transmit a `Viewport-Width: 320` header. Chrome only as the other browsers consider it harmful.
It doesn’t solve the problem, though. Font availability and subpixel rendering varies from OS to OS and browser to browser.
If the screen resolution and scaling is the same, and the operating system is the same, then you should get very consistent results across operating systems. They use the same algorithm, but subpixel hinting may differ slightly.
If you stick to metrically compatible fonts for the different operating systems, you’ll get almost identical results across OSes too (assuming same screen resolution and scaling). https://www.ctrl.blog/entry/font-stack-text.html
Windows Search is heavily cloud-dependent, and yes it’s performance suffers under poor network conditions.