badmintonbaseba

8 ms·

61.
by badmintonbaseba 2y ago
Blue noise threshold map works really well on GPUs.
62.
by badmintonbaseba 2y ago
Super interesting. Tempting to hook it up with conan to build our dependencies and set it up with our unit tests at least. If incompatibilities are mostly due to the libc then I don't think any of our C++ dependencies would care.
63.
by badmintonbaseba 2y ago
What modifications are needed to run through Fil-C, if any? It looks like you forked some of the software to run through Fil-C. Are you subsetting the language, or do those libraries/applications run into some "benign" UB und
64.
by badmintonbaseba 2y ago
What about performance?
65.
by badmintonbaseba 2y ago
Even if you limit "side effects" to observable behavior in the abstract machine sense, it's not entirely clear what is meant by a function to be "pure". GCC has two attributes for marking functions, "pure"
66.
by badmintonbaseba 2y ago
Apart from implementing it incorrect, an uncalibrated display could also cause this. Check out http://www.lagom.nl/lcd-test/gamma_calibration.php with DPI scaling turned off, at 100% zoom level (how browsers scale imag
67.
by badmintonbaseba 2y ago
I agree. I think the problem is a banal missing color transformation somewhere in the pipeline, like converting the palette and image to linear colorspace, doing the dithering there and mistakenly writing the linear color values instead of
68.
by badmintonbaseba 2y ago
That's a good point. I would argue that both that line and the reported `loop.run_until_complete(main_task)` line are important, but then it becomes impossible to have a single linear trace when there are manually scheduled and waited
69.
by badmintonbaseba 2y ago
Python asyncio supports meaningful stack traces through async functions just fine. import asyncio async def baz(): await asyncio.sleep(.1) raise RuntimeError() async def bar(): await asyncio.sleep(.1) a
70.
by badmintonbaseba 2y ago
I would be more interested in matching up timing/latency, especially with the OBS processing in the middle.
71.
by badmintonbaseba 2y ago
boost.beast also only talks HTTP/1.1 AFAIK, so if you want HTTP/2 or /3 on your frontend then you must put it behind a reverse proxy anyway.
72.
by badmintonbaseba 2y ago
The code is there to explain the comment.
73.
by badmintonbaseba 2y ago
I think it was downplayed even more. Supposedly the initial email by the researcher only had evidence for leaking database sizes, and I think it's likely that the CEO only got confirmation for this evidence internally and nothing more.
74.
by badmintonbaseba 2y ago
It looks like the CEO is both clueless and his reports are also probably misleading him. Whoever looked into the security problem probably saw the extent of it. This possibly got downplayed when reported back to the CEO. However rude, the C
75.
by badmintonbaseba 2y ago
The name of the tool is on point.
76.
by badmintonbaseba 2y ago
Presumably the author would like something that's handled by the kernel and not user space, so even a SIGKILL-ed parent process would trigger the reaping of the children.
77.
by badmintonbaseba 2y ago
My gripe was not the form of initialization of the elements, but forming `b.a1` before `b`'s lifetime has started. It hasn't started before all of the elements are initialized.
78.
by badmintonbaseba 2y ago
That's a stretch to call it "easy enough", you are explicitly pointing the gun at your foot. That `b.a1` might not be explicitly UB, but that's quite suspect when b's lifetime didn't start yet. Accessing member
79.
by badmintonbaseba 2y ago
It's mostly C++. You are right to be scared.
80.
by badmintonbaseba 2y ago
You can build runtime reflection on top of compile time reflection, it's impossible the other way around. Compile time reflection is a superset of what runtime reflection can do.
81.
by badmintonbaseba 2y ago
You can't easily take the pointer to an other member in a designated initializer. It's still a problem for members that are implicitly initialized by their default member initializer, but that can be sorted out.
82.
by badmintonbaseba 2y ago
> As far as I know, there is no way to actually force a C++ class to be heap allocated. Make the destructor (and possibly the constructors) private, have public factory functions that hand out unique_ptr with a custom deleter, or define
83.
by badmintonbaseba 2y ago
freestanding maybe? Embedded apps often don't shy away from using something like printf, yet they don't like unnecessary allocations.
84.
by badmintonbaseba 2y ago
Try https://www.youtube.com/watch?v=IUDTlvagjJA
85.
by badmintonbaseba 2y ago
> Since this is a major release, the Pixel 4a (5G) and Pixel 5 have not been ported to Android 14 QPR2 as part our initial release. We need to determine whether it makes sense to move these end-of-life devices to Android 14 QPR2 or keep
86.
by badmintonbaseba 2y ago
How is that supposed to work for second hand vehicles?
87.
by badmintonbaseba 2y ago
This just highlights how the security scanning is just theater though. So bad actors can now just have their evil content behind a form, and users get accustomed to the double opt-in workflow anyway.
88.
by badmintonbaseba 2y ago
> Why should they make which datacenters have a resource cached be obvious public knowledge? I agree that having it in the header for everyone is maybe too obvious. But you could otherwise infer that from timing.
89.
by badmintonbaseba 2y ago
Just recently apt listchanges informed me that "curl" (the binary) switched to gnuTLS to support HTTP3 (libcurl remained on openSSL for compatibility). So I assume this is still not fully resolved.
90.
by badmintonbaseba 2y ago
It's the combination of steering and forward momentum the gives the negative feedback. Bike tips left -> steering turns left -> circular path -> (from moving frame of reference) centrifugal force tips the bike back upright. Wi

More ›