How does it affect binary size? Node's SEA (embedding script+node into a single binary) is slowly maturing so smaller binary sizes would benefit distribution.
Just get a modern Sony TV and be done with it. They perfected Motionflow to the point where you no longer think about framerate (choppiness nor soap opera). It's clearly a priority, probably because they are the only manufacturer with their own studios (Columbia/Sony pictures). There is a reason people pay the $800+ Sony tax over any TV that has the same panel.
Newpipe is great for background listening and PIP (window can be resized/moved). For downloading, Seal reigns supreme. You can 'share' a video to the app and it downloads the video right away.
It makes sense from a business perspective. Get a 'brand' product instead of some obscure free PHP clone, so you can say you have assurances for business continuity through support/fixes/security patches. Price and the god awful performance aside.
Concerning, as their lingo would say. According to the below article this will also screw over open-source developers and data scientists:
Open Source LLMs Not Exempt:
Open source foundational models are not exempt from the act. The programmers and distributors of the software have legal liability. For other forms of open source AI software, liability shifts to the group employing the software or bringing it to market.
Dutch researchers claim the Japanese leaf flea, the natural enemy of the Japanese knotweed, can be used to combat it. The universe always rebalances itself.
Not a cryptophobe, but his rule seems reasonable: 'use it, but you won't get support if you use it for things I don't like'. Certainly better than the 'you may only use this product if you support/disavow $x' emerging trend in 'OSS' README's.