3 ms·
heh, I didn't expect to see poop on the front page of hacker news. If you're curious about the poop-making process, I created it and released it all on one 6 h
by AndyKelley 3y ago
heh, I didn't expect to see poop on the front page of hacker news.
If you're curious about the poop-making process, I created it and released it all on one 6 hour twitch stream [1].
[1]: https://www.twitch.tv/videos/1845437356 https://www.twitch.tv/videos/1845437356
- devsda 3y agoEven with the context, this comment sounded so intriguing and wrong at the same time that I hesitated while opening the link. Watched a few mins and bookmarked it for another day. There were many other name suggestions that are good but I'm glad you kept the initial name.
- notThrowingAway 3y agoNote that twitch VODs don't stay up forever, Andrew did mention that he would upload to peertube, but I don't know if he did.
- _yb2s 3y agoDoes this need a [NSFW] tag?
- DANmode 3y agoTwitch?!
- pkphilip 3y agoI know how to make poop, bro. Been doing it for a long time now.
- dundarious 3y agoKindof off-topic, but has anyone had any success in using perf_event_open from within WSL, or is that unsupported? I tried `sysctl kernel.perf_event_paranoid=0` and the following, which works under "real" linux, but fails under WSL: struct perf_event_attr attr = { .type = PERF_TYPE_HARDWARE, .size = sizeof(struct perf_event_attr), .config = PERF_COUNT_HW_INSTRUCTIONS, .disabled = 1, /* only need to read once, not updating values, but fails with 0 also */ .exclude_kernel = 1, .exclude_hv = 1 }; int fd = perf_event_open(&attr, 0, -1, -1, 0); /* fails, returns -1 */ Microsoft's kernel appears to have the right CONFIG_* as well, so I feel like it must be supported in some capacity, even if limited.