Recent submissions

Comment · 24 days ago
this is about 10,000x too much stuff for the equivalent feature set to a markdown file that your agent updates.
Comment · 2 months ago
Do you have examples of complex algorithms running on the gpu with rust with competative performance? Radix sort might be a good one to start with
Comment · 4 months ago
I don’t think this needed to be parallelized.
Comment · 6 months ago
I don’t understand why this is a useful effort. It seems like a solution in source of a problem. It’s going to be incredibly easy to end up with hopelessly inefficient programs that need a full redesign in a normal gpu programming model to be useful.
Comment · 8 months ago
This is an interesting line in the readme:

> The language forces clarity — not ceremony.

I find this statement curious because a language, like this, without ability to build abstractions forces exactly the opposite.

Comment · 9 months ago
In my mind, cad that you’re not going to manufacture is “modeling”. Not sure if that’s a common verbal distinction.
Comment · 9 months ago
Breps. Nearly all commercial cad packages operate on boundary representations of objects.
Comment · 9 months ago
Comment · 9 months ago
Incredible work!
Comment · 11 months ago
I don’t think it’s falsifiable until there are autism diagnostics that aren’t behavioral. Right now, they’re 100% behavioral, which that any theory that tries to cluster autism symptoms is hopelessly tainted by a recursive definition -> diagnosis -> definition cycle.
Comment · 11 months ago
I find this type of science is infuriating. Monotropism as a theory of autism or adhd is equivalent to saying that “tendency to focus on a few things” is a theory of autism or adhd. You’re describing the symptoms, which explains almost nothing. A theory of autism would explain the underlying physical causes of the behavior.
Comment · 1 year ago
As usual, GPT-1 has the more beautiful and compelling answer.
Comment · 1 year ago
> In this specific situation i constructed that precludes inlining of iterators and allows inlining of for-each, then iterators aren’t inlined.
Comment · 1 year ago
Sure. I can easily see that often being the case for arbitrary code but not interpreter dispatch loops.
Comment · 1 year ago
I must be missing something here. How would this help predict interpreter dispatch? Those won’t be a function of previous branch history or pc, which may very well be independent of the next opcode. They’d be a function of state in memory or registers.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton