Recent submissions

Comment · 14 minutes ago
Unfortunately for Copper in particular, .cu is associated with CUDA (so perhaps that’s why).
Comment · 8 days ago
I’d be curious to know why you feel like that. For me, it’s the opposite. In the sonnet version, the game takes up a much larger percent of the viewport and the ability to swipe to control the Pac-Man is leagues about the small directional arrow buttons IMO.
Comment · 17 days ago
It's interesting the high reasoning pelican is animated. I don't think I've seen another model do that before.
Comment · 1 month ago
Does this article not have a source?
Comment · 1 month ago
This is actually pretty cool. I think the undertalked about part of this for TypeSafe is that they can always "extract"/distill the frontier of this type of task from the newest LLMs for cheap. Jev seems seems to be GPT-6-Astra/Fable 5.1 but I imagine a bunch of training data is from earlier models?

Then, you can serve it faster/cheaper than the frontier LLMs. It's basically distilling a small but extremely common use-case from LLMs and serving it. Then RLCD comes into play to update weights when a new model comes out, etc.

Any thoughts on what the next potential "cheap" win to be distilled from frontier LLMs is? I'm going to need to play around with this.

Comment · 1 month ago
I don’t think it was misleading, deliberately or otherwise. Did you read the report? I hate to call you out like that but I think you can only get that impression if you only read the above quotes. That’s not the insinuation I get at all. It’s specifically under the “illicit distillation” category. It’s never framed in anyway but as a form of distillation.

I think they are pretty fair and explicitly say “Distillation itself is a legitimate training method […] Distillation is commonly used because it reduces the resources needed to achieve more advanced capabilities”. And go on to say their definition that makes it illicit in these cases.

And, also, they almost certainly __were__ tricking users and sending their data overseas.

Do you see it any differently?

Comment · 1 month ago
Heads up: it doesn't appear to be available on the Devin CLI (for me as a free user).
Comment · 2 months ago
Cool demo! That's funny. I literally sketched out something similar 30 minutes ago on paper. I wonder if there was some recent, semi-related article/link that subconsciously prompted the relevance.
Comment · 3 months ago
>I also worked on all of the copy myself, collecting feedback from core maintainers as I went. The new tagline was a suggestion from Theo which we iterated on. I did use LLMs as an assistant, but I did not ask it to generate the content.

>Might as well use LLMs for the whole thing next time, since we will be accused of doing so anyway! :D

Comment · 3 months ago
I generally agree with you that choosing something based on where it's hosted is dumb. I still think there could be an impact wrt a network effect.

The original comment you replied to was talking about "the loss of network effect" and you sounded dismissive of it. It might not even matter, but I think it's somewhat fair to say it could have an impact.

Comment · 3 months ago
I agree. It's possible in the future a project hosted on codeberg is a silent "stamp of quality". Though, I still think there could be impact wrt a network effect.
Comment · 3 months ago
You’re telling me you would be as likely to contribute to a project hosted in CVS as compared to git (and on GitHub)?
Comment · 3 months ago
“An Ad hominem refers to when a speaker attacks the character, motive, or some other attribute of the person making an argument rather than the substance of the argument itself”

It’s definitionally an ad hominem against Jared. If he stuck to why he thought it was bad for Bun to do this, I would be more sympathetic.

Comment · 4 months ago
Comment · 6 months ago
A quote from the official FAQ - https://github.com/microsoft/typescript-go/discussions/411:

>By far the most important aspect is that we need to keep the new codebase as compatible as possible, both in terms of semantics and in terms of code structure. We expect to maintain both codebases for quite some time going forward. Languages that allow for a structurally similar codebase offer a significant boon for anyone making code changes because we can easily port changes between the two codebases. In contrast, languages that require fundamental rethinking of memory management, mutation, data structuring, polymorphism, laziness, etc., might be a better fit for a ground-up rewrite, but we're undertaking this more as a port that maintains the existing behavior and critical optimizations we've built into the language. Idiomatic Go strongly resembles the existing coding patterns of the TypeScript codebase, which makes this porting effort much more tractable.

TLDR: Typescript -> Go is much easier than Typescript -> Rust/Zig/$OTHERNATIVELANG

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton