ta3401

4 ms·

1.
by ta3401 2y ago
Imho, a good type system for scientific computing will let you check that your computations are well formed. For instance, if one tries to apply a matrix to a vector of the wrong size, the type system should report it, or rather one should
2.
by ta3401 2y ago
> which may avoid tearing (though I don't see why) What I meant here is that I didn't see why asynchronous updates may introduce tearing; but my tired brain couldn't quite formulate it properly. And to answer that, it&#x27
3.
by ta3401 2y ago
I now realize that I somewhat rephrased what was said in the blog. How strange!
4.
by ta3401 2y ago
> But it then talks about how exp is implemented in hardware, in a way that forces it to be a non-SIMD calculation. The fact that exp is implemented in hardware is not the argument. The argument is that exp is a library function, compile
5.
by ta3401 2y ago
Perhaps not in the sense of weak vs strong, but rather in weak vs powerful. C type system isn't very powerful, if you compare it to languages from the scientific community (Python is an exception here imho). It is simple and probably g
6.
by ta3401 2y ago
Thank you. So, if I get this right, the cursor position, which is what the video card needs to position the mouse pointer picture on the screen as an overlay to the actual framebuffer, isn't updated asynchronously to the screen update
7.
by ta3401 2y ago
> Anyway, what you refer to is the legacy drm interface that was replaced by the atomic one. The legacy interface is very broken and does not expose new hardware features, but it did indeed handle cursors as its own magical entity. Isn&#