glowcoil

8 ms·

1.
Simplifying the build process for vst3-rs(micahrj.github.io)
1 points by glowcoil 9mo ago|0 comments
2.
by glowcoil 1y ago
I'm sorry, but even if I am maximally charitable and assume that everything you are saying is meaningful and makes sense, it still has essentially nothing to do with the original article. The original article is about imposing constra
3.
by glowcoil 1y ago
The original article discusses techniques for constraining the weights of a neural network to a submanifold of weight space during training. Your comment discusses interleaving the tokens of an LLM prompt with Unicode PUA code points. These
4.
by glowcoil 1y ago
I would recommend reading beyond the title of a post before leaving replies like this, as your comment is thoroughly addressed in the text of the article: > At this point you might be wondering, isn’t this a problem in many languages? Do
5.
by glowcoil 2y ago
You originally described a problem where fog had a different falloff in world space at the edges of the screen compared to the center of the screen. The root cause of that is not the perspective projection; it's how the fog is being
6.
by glowcoil 2y ago
The only physically accurate answer for where to put the far plane is "behind everything you want to be visible". It fundamentally does not make any sense to change the shape of the far plane to "more accurately reflect human
7.
by glowcoil 2y ago
You're describing a problem with a particular method of fog rendering. The correct way to address that would be to change how fog is rendered. The perspective projection and the far plane are simply not the correct place to look for a
8.
by glowcoil 2y ago
It's not. Why would it be?
9.
LLQ: A wait-free SPSC linked-list queue with recyclable nodes written in Rust(glowcoil.com)
4 points by glowcoil 4y ago|0 comments
10.
by glowcoil 4y ago
> The model of treating each variable as stack-allocated until proven (potentially fallaciously) otherwise is distinctly C brain damage. OK, let's consider block-local variables to have indeterminate storage location unless their ad
11.
by glowcoil 4y ago
> If you write code that tries to get a pointer to the first variable in the stack, and guess the stack size and read everything in it, Odin does not prevent that, it also (AFAIK) does not prevent the compiler from promoting local variab
12.
by glowcoil 4y ago
The compiler is already doing that when it performs any of the optimizations I mentioned above. When the compiler takes a stack-allocated variable (whose address is never directly taken) and promotes it to a register, removes dead stores
13.
by glowcoil 4y ago
This is fundamentally the same thing as undefined behavior, regardless of whether Odin insists on calling it by a different name. If you don't want behavior to be undefined, you have to define it, and every part of the compiler has to
14.
by glowcoil 4y ago
Frankly it seems strange to me to be comparing Vale's generational reference system and Rust's borrow checker directly. They have completely different characteristics and are not direct substitutes for one another. First, Rust&#x2
15.
by glowcoil 4y ago
I and some other folks in the Rust audio community have put together some low-level bindings for the CLAP API: https://github.com/glowcoil/clap-sys They're relatively straightforward due to the fact that CLAP is a
16.
by glowcoil 4y ago
RAII is a general pattern for tying resource management to the lifetime of objects such that resource allocation is tied to value construction and resource deallocation is tied to value destruction. The smart pointers for allocation in the
17.
by glowcoil 4y ago
You can't use RAII in Rust? What on earth could this possibly mean? RAII is an extremely pervasive pattern in Rust and is fundamental to many of the safe APIs in the standard library.
18.
by glowcoil 5y ago
You are missing something. For a piece of Rust software to run in any widely used computing environment, it is required to interface with a large body of non-Rust software via a non-typechecked ABI. Moreover, the Rust standard library itsel
19.
by glowcoil 5y ago
> There has been an explosive growth in component software technologies since the first edition of this classic book was published. The advent of EJB, J2EE, CORBA 3, COM+ and the .NET framework are evidence of a maturing market in compon
20.
by glowcoil 5y ago
Yes, Concurrent ML exists. It also, however, does not have any feature analogous to Rust's Send trait or Swift's Sendable protocol.
21.
by glowcoil 5y ago
The things you are saying are just not true. Standard ML and OCaml are in fact single-threaded languages, and while Haskell has concurrency and parallelism support it does not have anything that looks particularly like a Send or Sendable tr
22.
by glowcoil 5y ago
There is really no way in which Rust's Send or Swift's Sendable form a monad or a functor in any of the senses of those terms.
23.
Basedrop: A garbage collector for real-time audio in Rust(glowcoil.com)
10 points by glowcoil 5y ago|0 comments
24.
by glowcoil 6y ago
The document explains above the tiger image (like, directly above it) that it is a test image meant to evaluate a hypothesis about fragment shader scheduling: > Update (7 May): I did a test to see which threads in the fragment shader get
25.
by glowcoil 6y ago
> > This makes it clear you didn't even perform a cursory investigation of the project > I did, and mentioned in the docs, here’s a quote: “I didn’t want to experiment with GPU-based splines. AFAIK the research is not there ju
26.
by glowcoil 6y ago
> The quality is not good, and the performance is not even mentioned. I notice that your renderer doesn't even attempt to render text on the GPU and instead just blits glyphs from an atlas texture rendered with Freetype on the CPU:
27.
by glowcoil 6y ago
This isn't really accurate; the immediate-mode approach you're talking about was deprecated in OpenGL 3.0 and was never supported in OpenGL ES, and in fact, Direct3D started out with an immediate-mode API just like OpenGL before m
28.
by glowcoil 7y ago
You can just switch from "Home" to "Latest Tweets" and all of this goes away.
29.
by glowcoil 7y ago
I don't think they actually take luminance into account (although I personally like the idea); I just meant that they solve the problem of "black-on-white text looks too thin" by thickening the text, rather than messing up ot
30.
by glowcoil 7y ago
As a simple demonstration, here's an image of a 1px white-on-black line and a 1px black-on-white line: https://imgur.com/a/9d9Tu3x It's axis-aligned and box-filtered so there are no shades of gray, which mean

More ›