Because it's an easy solution esp. to a rather new installer: setting up swap on disk (partition or file, if file which file system, if partition w/o encryption, ...). Zram: install one additional package and forget.
See also the "zram on Fedora" section in the article.
Which ones? Translation is local. Preview summarization is local. Image description generation is local. Tab grouping is local. Sidebar can also show a locally hosted page.
> In theory Intel and AMD would pay the HEVC fees once
> In practice it seems everyone in the value chain are forced to pay, Intel, AMD, Nvidia, HP, Dell and then even browser and software.
The fee is payed by the one who makes it "available" to the enduser. AMD and Intel pay nothing, they implement "math" accelerating it, but they do not "provide" it to a customer. The fee is collected by the last one in the chain enabling it for the customer.
So Dell selling a product supporting it out of the box as a complete "experience" is the last in the chain. If e.g. Dell doesn't support it and the user acquires the "enabling piece" from the Microsoft Store, then Microsoft has to pay it. That's why U.S. based Linux distros (backed by a company) disable the codecs, because they would be the last in the chain (e.g. by shipping the "enabler" through mesa). For the same reason Firefox would be on the hook, if they ship the "enabling" part - which they get around for h.264 by providing a blob payed by Oracle or relying on the OS facilities for h.265.
> Also, nuclear reactors don't deplete water for cooling so the premise of this article doesn't make sense. It goes from water to steam, to rain, back to water.
The premise of the article is pretty clear: It's a statistic about how much raw material was extracted by the industry. Nothing more, nothing less.
There's also the number for agricultural consumption. But somehow we don't need a huge disclaimer about the water cycle to prevent hurting people who like agriculture.
Twitch did in the past (mostly), but it is trying pivot at the moment: Take tight control over the encoding settings on the client side and just pass the already encoded stream through the CDN. https://help.twitch.tv/s/article/multiple-encodes
Also having different encoding settings for different purposes is desired (e.g. high quality local recording for an edit later while live streaming to different services at the same time [Twitch, Youtube, ...]).
That said, I'm not aware of Intel limiting the number of encoding streams, so I don't know where the number 2 originates.
It changes the color, but that color has no inherent meaning. Let's eradicate any prior knowledge of what was clicked. Let's say you make screenshot of the current state, and show that to a random person on the street, who has never used FF before.
What are the odds of that person identifying what is currently active?
If the counter is "you know because you remembered" or you "know because you learned" then any of these answers indicate a inferior and non-intuitive UI design.
I moved on to sideberry and hide the normal tab bar completely. But if you open two identical tabs in the default layout I have no clue which one is active anymore. You can't understand that UI, you have learn it. It's infuriating.
PS: The core of Valve's technical contribution is around the SteamDeck. You already know it runs Linux, Proton, yadayadayada. An obvious fact that only clicked for me after being mentioned in the presentation: if you aren't in the Steam store but want your app on the SteamDeck the primary option is a Linux version (distributed through flatpack). That (commercial) incentive alone is a huge benefit. Suddenly you can make a business case why your product maybe should support Linux.
See also the "zram on Fedora" section in the article.