55 karma · joined December 28, 2025
to the point that Apache web server developers added a custom rule in the default httpd.conf to strip away incoming DNT headers !!!
https://arstechnica.com/information-technology/2012/09/apach...
this way all the RAM that AI data centers scoop up will be used to lessen demand for RAM that those same datacenters created
net-zero RAM!
it's why GPUs have their memory chips in a circle around the GPU chip.
why dont you run the VM on your machine?
but if it's like using a Dvorak and a Qwerty at the same time, it makes sense it should be the only device
how the OS implements what is displayed is irrelevant
windows has all kinds of virtualizations today, it can literally run web views in separate (invisible) VMs for security purposes
I've worked with all major GUI frameworks, from MFC to Qt, they all suck compared with React/Vue
not sure if that makes them a power user
why do you equate second device with digital detox?
what happened to use the best tool for the job? use a phone with a physical keyboard when chatting on WhatsApp and then switch to a regular phone for Instagram and browsing web. not saying everybody should do this but if chatting is your life...
some people even use a phone and a laptop at the same time, they are already a second device person, so they could be a three device person
the power user base you mention is probably too small to sustain them long term
hardware encoders (like the ones in GPUs) typically work realtime-ish, so they do minimal exploration of encoding space
you also have the one-pass/two-pass thing which is key for unlocking high quality compression
what will stop you then from keeping your existing TikTok phone after buying this?
you can fight that, and lose (no market)
or accept second device status (for werk), optimize that use case, and be honest that it will not be the main device
but across many consecutive frames, the information is spread out temporaly and can be recovered (partially)
the same principle of how you can get a high resolution image from a short video, by extracting the same patch from multiple frames
the compressor (encoder) decides exactly how to pack the data, it's not deterministic, you can do a better job at it or a worse one
which is why we have "better" zlib implementations which compress more tightly
video has certain temporal statistics which can allow you to fit the missing information
only true blurred white noise is impossible to recover
if you expand limited YCrCb to a large HDR range you'll get a "blurred" output.
Imaging converting 1 bit image (0 or 1, black or white pixel) to full range HDR RGB - it's still black and white
your comment above has the same broken formatting
does not inspire confidence if you can't spot such obvious breakage