Hacker News

Top stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. Nokia Design Archive (2025)(aalto.fi)
    23comments
  2. Linux support is coming to Snapdragon X2 Series(qualcomm.com)
    187comments
  3. Claude discovers a novel enzyme system with CRISPR-like repeats(anthropic.com)
    680comments
  4. Starlink ground station in Poland hit by fire in suspected arson attack(notesfrompoland.com)
    21comments
  5. Ideas on modernizing the open-source desktop(lwn.net)
    165comments
  6. RAM: the forgotten history (2024)(coredump.cx)
    discuss
  7. Meta takes down a critical video about meta AI Glasses after filming at Meta(reddit.com)
    75comments
  8. Early rogue AI agent activity and attempts to hack found on urlquery.net(transluce.org)
    119comments
  9. ArXiv receives multiyear commitments to support it as an independent nonprofit(arxiv.org)
    24comments
  10. Contrastive Language Models(contrastive-lm.notion.site)
    18comments
  11. VSCode's SSH Agent Is Bananas (2025)(fly.io)
    151comments
  12. The "Windows XP Box" (2003)(mini-itx.com)
    29comments
  13. Virtio-nvgpu: Near-native Nvidia GPU access inside a KVM guest(github.com/nestrilabs)
    46comments
  14. Fixing the Portobello Police Station Clock(pointinthecloud.com)
    103comments
  15. OpenAI agent hacked Australian government website, PM says(bbc.com)
    44comments
  16. Women Who Sold Books Door to Door(jstor.org)
    discuss
  17. Why 'What's Opera, Doc?' looks like that(animationobsessive.substack.com)
    15comments
  18. Making portable my unportable transputer C compiler(nanochess.org)
    4comments
  19. Mercury 2.5 LLM hits 770 tokens per second(artificialanalysis.ai)
    68comments
  20. Meta VR Glasses(meta.com)
    369comments
  21. Making Tailscale Faster(tailscale.com)
    69comments
  22. Automated optimization of a molecular simulation program(shishir-iyer.medium.com)
    discuss
  23. Looks promising for document editing with your agent(paperinstruments.com)
    discuss
  24. The mystery animal on an ancient god's head(signoregalilei.com)
    35comments
  25. A brief history of Windows scroll bar shortcuts(devblogs.microsoft.com/oldnewthing)
    85comments
  26. Tokens too cheap to meter(jyn.dev)
    207comments
  27. Solving for faster SHA-1 collision detection(sam.dev)
    9comments
  28. Italian parliament votes for return to nuclear energy(apnews.com)
    639comments
  29. Show HN: An open-source manufacturing ERP/MES/QMS(carbon.ms)
    17comments
  30. Gemini 3.8 text-to-speech(blog.google)
    138comments

Contrastive Language Models

85 pointsby 7h agocontrastive-lm.notion.site
18 comments
6h agoHN ↗

I wonder when work started on this project, and how the public release of Jev played into their timing.

5h agoHN ↗

Does the latency even matter?

You're comparing a local GPU to network hops? Wouldn't be surprised if Jev was actually similar in runtime and their is just a great deal of network latency.

The evaluation is quite interesting though - I'd actually say the raw answer is correct in the absence of detail and prior knowledge (Who wrote the play Romeo and Juliet).

4h agoHN ↗

I tried TypeSafe’s Jev playground. It outputs the model latency and network latency separately. The model latency was 100-200ms in my tests.

5h agoHN ↗

what's with that dino run? Jev is slow but it jumps correctly, their model always touches the cactus or whatever it is...I am guessing it doesn't matter? Or does it?

4h agoHN ↗

Very interesting insight on the training process, it's pretty cool to have some experimental justification for why they took these exact steps, what they tried and did not work, etc. Feels a bit less like dark magic.

However I agree the latency argument doesn't hold much value with Jev because it runs on a remote server. Seeing how many open Jev-like models came out recently it would be much more interesting to have a comparison with them.

3h agoHN ↗

"On par with Jev" is Mario, T-Rex, WikiRacing: large-K semantic action matching, the regime where cosine over independently encoded vectors is the right inductive bias. The zero-shot suite does not cover the typed-decision load: date arithmetic, negation chains, policy thresholds.

3h agoHN ↗

I really hope that "System One" won't stick around as a new buzzword simply meaning "fast".

2h agoHN ↗

i'm well aware of the origin and meaning of the term

"System 1" is fast, instinctive and emotional

this implies more than just "fast", which is precisely why i don't like its present usage

2h agoHN ↗

Instinctive is a good way to describe it compared to generative LLMs. Jev gives you one instant answer, fast and usually correct but without nuance or any explanation. Human instincts work the same way.

1h agoHN ↗

In my testing Jev is not what I would call "usually correct" on most topics that involve knowledge of the world outside of the context you give it.

47m agoHN ↗

You're describing external aspects but to me, "instinct" says much more about internal processes than the properties you mentioned, and I haven't seen anything that tells me how these models draw on anything similar to these internal processes to generate their outputs (at least not more than generic LLMs do)

6m agoHN ↗

I think System 1 is a great term. System 1 is fast, intuitive, and automatic. It describes decision-making that happens without explicit reasoning or deliberation. System 2 is the opposite: it's the more deliberate, "executive functioning" side of cognition -- the part that reasons through a problem before arriving at an answer. That's also what state-of-the-art LLMs do before they respond. Jev doesn’t do that kind of reasoning. It just decides.

3h agoHN ↗

I tried running this on a H100 and got 190ms compared to Jev's 170ms. Maybe I set it up wrong?

2h agoHN ↗

I’m fascinated by this thing and by the way it’s interpreting Jev. It’s very cool, but is it actually a classifier?

IIUC they took an already-trained “frozen” LLM and trained a little model on top that takes both a question and the hidden states after processing the input data and produces answer “probabilities”. (In contrast, the original LLM would have been run in AR mode to generate multiple output tokens representing its answer.) But then they used it for a purpose that isn’t really classification.

IMO there is a rather large difference between “is this email spam” and “what character should I type in this agentic workload”. The former is classification: there is hopefully a ground truth (is the email spam?) and the model is trying to classify the email. You would score it with a proper scoring rule. The latter is a strategy: there usually isn’t a correct answer, now or in the future. The model is playing a game consisting of repeated rounds, and the only way to evaluate it is to see how well it plays. You can’t even usefully compare it to the optimal solution because you may not know the optimal solution and you don’t actually need the model to produce an optimal solution.

I do think this approach is really cool, and it does suggest that one might be able to use a modern LLM to process an input and then extract the model’s next agentic step in a very fast, non-AR manner, with results comparably good to the usual AR decoding. And I think it’s very interesting to decouple the tokenized input representation from the model output representation, both because prefill tends to be faster and cheaper than AR output and because it’s never seemed particularly sensible to me that a model should be constrained to generate outputs at the cadence of one run through the model per output token. (AFAIK the main reason that models work on the same input and output token space is that this is how the pretraining process works.)

I wonder how to fit “reasoning” into this framework. Maybe have the question be something like “do you need to think further and, if so, what is your first thinking token”. But maybe something more clever is possible.

1h agoHN ↗

I'm increasingly of the opinion that stuff like Jev and this are overfitting and producing illusory but confident "probabilities" that are complete bullshit. You can't see the underlying reasoning... but it's incredibly tempting for people who want to place faith in them. Rather than even trying to understand the complex system at play, it's easy to give up on trying to find reason, and just accept the second- or third-tier outputs of massively complex things that, on the first tier, are not necessarily reliable sources of truth.

Let's give an example: Suppose you ran a Jev that tried to determine when another Jev was wrong about something ...baseball games, let's say. The second Jev would come up with a perfect list of when the first Jev was wrong and when not to believe it. So now you have a second-order system that you believe more than the first-order one.

Only after 100 baseball games, the second-order Jev is only as good as the first one, it just inverted a bunch of games that could have gone either way. So hell, you make a third-order Jev that analyzes the first two...and its results are AMAZING when you look at the historical record! Only, you know, that's what's called overfitting.

Honestly, the invention of the "noul" is a bit of a giveaway. Imagine what junk bond traders could've done with that in the '80s. Not-not-not-falsy is how we all like our stock picks served up, right?

Reading the raw statistical output of an LLM as if it were an oracular source of truth is literally idol worship and gambling in the purest sense.

Take it from a guy who lost $10k on baseball this season having Claude rewrite my original code to reverse and re-reverse underdogs and favorites; there is no fucking "probability" of anything coming out of an LLM, even if your source of truth isn't an LLM but an evolutionary algorithm you designed yourself. Which would've performed better before the LLM started interpreting ways to bucket it and make up bullshit probabilities around it.

Anyone going down the Jev path is deeply misguided, but will see the light once they realize they have re-invented the magic 8 ball. Or that executive decision maker cube from the 80s with 6 random answers.