Hacker News .hnnew | past | comments | ask | show | jobs | submit | LordJZ's commentslogin

Not really: `select sql from sqlite_master` still reveals the solution.


For me it shows the hexcode of the name but not the name itself.


yes


Thanks, this looks great. I can only wish it had RSS.



This broke the sidebar splitter hide CSS:

``` #sidebar-splitter { display: none } ```

To fix add this: ``` vbox#sidebar-box.chromeclass-extrachrome[src] { border-right: none !important } ```


This is false.


Well, I guess that decides it


The thing is, anyone with a 144 Hz monitor [1] knows from experience that what you're claiming here is complete bullshit. Then there's also the fact that 70 Hz causes demonstrably more nausea in VR users than 90 Hz or more.

Beyond that, if you wanna act innocent and play a citation game, I can throw you a bone. I'll give you this [2], what do you give me in return?

--

[1] This was already evident back in CRT days when 70 Hz was garbage and 100+ Hz was what every serious gamer was after.

[2] http://www.100fps.com/how_many_frames_can_humans_see.htm


Really? Your first citation is youself[1] and the second one is a random website that's clearly not scientific or published.

How about the NIH? https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2826883/figure/...

Gap detection thresholds for different age ranges. Notice that the average for vision is around 20ms, or 50fps. Yeah some people are lower but the large majority of people don't see any faster than 60fps

[1] so its not actually a citation it's just annoying.


This gap detection tests pretty much the same thing as CRT flicker. It tests at which point does a light source seem continuous. This doesn't cover the full extent of human vision capabilities. What's more, if you wouldn't have dismissed my link as "random" and actually read it, you would have seen that it covers this very same case and gives pretty much the same numbers. It's under Test 2: Sensitivity to darkness.

I could explain further, but I get the feeling that you've made up your mind and aren't willing to read much. If you change your mind, start with the link I gave earlier. [1]

In addition, this thing is pretty easily testable with home equipment. Get yourself a 144 Hz or faster monitor and construct the following program with OpenGL: two identical boxes moving side-by-side, one updating its position at the full 144 Hz and another at 60 Hz. [2] You'll see the difference yourself.

--

[1] http://www.100fps.com/how_many_frames_can_humans_see.htm

[2] There's a web app as well, but unfortunately browsers don't support frame rates higher than 60 Hz that well. My chrome is limited to 60 Hz even on 144 Hz for example. https://www.testufo.com/#test=framerates


And then there's Tizen which is even worse than Android Smart TVs. Dad bought a Samsung Smart TV with Tizen (even though I begged him to change his mind and buy a better solution for half the price) and expecting the worst I was _still_ suprised what an absolute piece of garbage that TV is.


Here's what I've been using, in addition to all the manual stuff and things like Destroy Windows 10 Spying[1]: https://gist.github.com/LordJZ/70d463335b2b7ab06e4f (still contains some stuff from DW10S because I started collecting snippets before it was released)

Feel free to contribute.

[1] https://github.com/Nummer/Destroy-Windows-10-Spying


It would be so kind of you to create an github issue for things you find ILSpy gets wrong. https://github.com/icsharpcode/ILSpy/issues


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: