take6056

So, I bought an RX 7600 XT, when I was still using my 10 year old TV. Recently upgraded to an LG C4, reading the news about AMD support for HDMI 2.1 on Linux, I also went looking for a DP->HDMI adapter and found one that claims to even support VRR. After a week of getting random audio cuts, suspecting the adapter was at fault, I went pure HDMI...

To my surprise, I could run at 4K 120hz with VRR and HDR. Doesn't that require HDMI 2.1?

TLDR: Why do so many routers support >1Gbit/s on their WiFi while only having 1Gbit/s ethernet interfaces?

So, I've been upgrading parts of my home setup and have a router (without AP) that has 2.5G interfaces. My PC also has a 2.5G interface, but that only going to the router is kinda useless (the ISP offers 1G).

The place my PC is at is also a good position for an AP. So, I went looking for a cheap second hand wifi router and stumbled upon quite a few that were boasting >1G connection speeds, not only AX but also AC. Now I know this is often a combined theoretical Max, but still a lot offer >1G for the single band.

The vast majority of these routers, though, have 1G Ethernet ports. Putting that between my PC and router reduces that linkspeed and I can't actually reach over 1G for the WiFi devices as well. Why would you sell a product like that. Undoubtedly those radio's were more expensive but their in a package that can't fully utilize them. I can think of some reasons: marketing, radio's are mostly not fully utilized anyways, helps with latency, maybe?

Does anyone know why it's done like this?

Apparently my setup, running the steam deck UI for gaming on my TV, is registering as an actual steam deck. Also unfortunate that the non steam games don't count, but hopefully next year this will be all purple/blue.

TLDR; Does anyone know if there's an initiative to use the pdf rendering engines built into most browsers and used while printing a web page in more flexible ways? Ideally from javascript being able to get the pdf as a File.

I've been looking into download as pdf functionality we implemented at work. It's for a single project, relatively small, so we implemented it with html2pdf.js. There seems to be no better way than rendering the webpage as canvas and saving as an image inside PDF. Although I'm thankful that the project exists, with the lack of text selection, poor image quality and/or large file sizes, it feels bad serving it to the customer. Then I started to look into the printed version and I loved it. Learned some new stuff about css, being able to break a page before a specific element. Tables automatically repeat their header across a page break. I can also save this as pdf, better quality, 40x reduction in file size, yay! However, web api to start this is print(), no arguments, no alternatives. Putting this behind a "Download" buttons seems confusing for the end user. I'm amazed we can't use this built in pdf rendering engine in more flexible ways. (See TLDR for question)