maggit
Joined 18 years ago
Karma
1,755
Submissions
340
Member since
Oct 14
https://magnushoff.com
View on Hacker NewsRecent submissions
Comment · 3 months ago
It's worth noting that Swiftfin finally had a new release for tvOS this summer which is worth checking out if you're interested in Jellyfin on Apple TV
Comment · 10 months ago
It is indeed badly aliased. The technique demonstrated does not take into account antialiasing in the initial render, which causes this issue. There are ways to improve it, but I would advise against this approach in general since it doesn't handle these edge cases well.
Comment · 1 year ago
x86-64 introduced a `syscall` instruction to allow syscalls with a lower overhead than going through interrupts. I don't know any reason to prefer `int 80h` over `syscall` when the latter is available. For documentation, see for example https://www.felixcloutier.com/x86/syscall
Comment · 1 year ago
There was a Minesweeper on here that used a SAT solver, but I cannot find it at the moment. As I recall, it never had any issue with resolving the board quickly. I think it dynamically resolved where the mines would be as you played the game, and if you clicked a square that could be a mine, it would be a mine, except, I believe, when there were no open squares that were safe.
(Edit: Here it is! https://pwmarcz.pl/kaboom/ And the write-up: https://pwmarcz.pl/blog/kaboom/ )
This is similar in spirit to my take on the game: https://magnushoff.com/articles/minesweeper/
Unfortunately, not being familiar with SAT solvers, my implementation can grind to a halt in some configurations :)
Comment · 1 year ago
It's more a matter of your personal preference and previous exposure to different languages. The way Rust reads is one of its super strengths in my book. I also really enjoyed Standard ML in university, and Rust picks up some of that (via OCaml).
Comment · 1 year ago
Adding some detail to this: With three buffers, you have one front-buffer (what's currently visible on screen) and two back-buffers. Let's call them A, B and C, respectively. This lets you work on the next frame in, say, B, and when it's ready, you queue it up for presentation. At the right time, then, the roles of the buffers will be switched, making B the front-buffer and A a back-buffer.
The third buffer comes into play if you want to start working on the next frame _before_ the switch has occurred. So you start drawing in C, and if the right time should hit, the display system can still flip A and B. In this case, triple buffering gave you a head-start with drawing the frame in C.
Going further, if you complete the frame in C still before the A/B switch has happened, you queue up C as the next frame, instead of B. Then, you can start working on the next frame again in B. With this scheme, there is no sense in having more buffers than three.
Comment · 1 year ago
Exact integers doesn't seem to be its strong suite. Can it even represent 3 exactly?
Running code from the linked notebook (https://github.com/AdamScherlis/notebooks-python/blob/main/m...), I can see that a 32 bit representation of the number 3 decodes to the following float: 2.999999983422908
(This is from running `decode(encode(3, 32))`)
Comment · 1 year ago
That's true for normal binary encoding of integers, but I think we should understand the question in context of the post: What's the number of bits required in iterated log coding?
Comment · 1 year ago
Cute! I wonder if it would be amenable for use as a variable-width encoding for, say, DCT coefficients in a JPEG-like codec..?
Comment · 2 years ago
I have realized that there is a big design space here, as I recently did a write-up of my take, Id30. 30 bits of information encoded base 32 into six chars, eg bpv3uq, zvaec2 or rfmbyz, with some handling of ambiguous chars on decoding.
Comment · 3 years ago
There's 12 parts to this in total:
1. https://pharr.org/matt/blog/2018/04/18/ispc-origins
2. https://pharr.org/matt/blog/2018/04/19/ispc-volta-is-born
3. https://pharr.org/matt/blog/2018/04/20/ispc-volta-going-all-...
4. https://pharr.org/matt/blog/2018/04/21/ispc-volta-c-and-spmd
5. https://pharr.org/matt/blog/2018/04/22/ispc-volta-first-resu...
6. https://pharr.org/matt/blog/2018/04/23/ispc-volta-users-and-...
7. https://pharr.org/matt/blog/2018/04/25/ispc-volta-avx
8. https://pharr.org/matt/blog/2018/04/26/ispc-volta-more-on-pe...
9. https://pharr.org/matt/blog/2018/04/27/ispc-volta-open-sourc...
10. https://pharr.org/matt/blog/2018/04/28/ispc-talks-and-depart...
11. https://pharr.org/matt/blog/2018/04/29/ispc-retrospective
Comment · 3 years ago
"System Integrity Protection (SIP)" seems to be the correct name here, for anyone as confused as me :)
(More details here: https://support.apple.com/en-us/102149 )
Comment · 3 years ago
Ah! That's what got me. Private mode is my default. I can confirm that I get it working in Firefox outside of private mode. Thanks :)