- Joined
- Feb 20, 2019
- Messages
- 8,339 (3.91/day)
System Name | Bragging Rights |
---|---|
Processor | Atom Z3735F 1.33GHz |
Motherboard | It has no markings but it's green |
Cooling | No, it's a 2.2W processor |
Memory | 2GB DDR3L-1333 |
Video Card(s) | Gen7 Intel HD (4EU @ 311MHz) |
Storage | 32GB eMMC and 128GB Sandisk Extreme U3 |
Display(s) | 10" IPS 1280x800 60Hz |
Case | Veddha T2 |
Audio Device(s) | Apparently, yes |
Power Supply | Samsung 18W 5V fast-charger |
Mouse | MX Anywhere 2 |
Keyboard | Logitech MX Keys (not Cherry MX at all) |
VR HMD | Samsung Oddyssey, not that I'd plug it into this though.... |
Software | W10 21H1, barely |
Benchmark Scores | I once clocked a Celeron-300A to 564MHz on an Abit BE6 and it scored over 9000. |
I'm sorry. But your graph over time is wrong. A CRT doesn't work the way you tried to paint it. You would need to know how a CRT is built to know how it works and why some people got headaches.
That's how a CRT works, measured at a specific point on the screen.
For the screen as a whole, the output from the electron gun is constant, but your retina doesn't focus on the whole screen at once, your macula focal region is a 5° cone of vision, and your monochrome periphery vision is even more sensitive to rapid contrast and brightness variance, which is why you can notice flicker in your peripheral vision sometimes but not when you stare directly at the source.
You're sorry? No, you're just plain wrong - I spent five seconds to double-check I was right and this was the very first google result. If you're going to attempt to patronise someone, please make sure you have a clue what you're actually talking about, at least take the five seconds to check yourself before wasting 20 seconds typing something wrong in a condescending tone.
(source link)
Last edited: