I totally can't sleep now....

The clip posted with this case (hosted by the collector’s media CDN); original post on X · 31s.

Matched 15 brands to real-time news hooks and applied intent labels across 428 items in 28 seconds, comparing Jev against DeepSeek.

The original post, translated

I totally can't sleep now.... This video lets you completely understand JEV's terrifying capability

I actually demonstrated it, using JEV and DeepSeek to do the same task: from the massive real-time news stream of the day, quickly match for 15 brands whether there are suitable PR hot topics to piggyback on, and tag them with structured intent classification labels

The result is: within 28 seconds, Jev blasted through a full 428 pieces of data, and completed all the goal decomposition and classification; while at the same time, DeepSeek V4.1-flash running on the same task had only just completed 6/428 items

The speed gap was widened by dozens of times, and the answer even returned before you finished reading the first line....

Why is there such a terrifying gap? The underlying logic is:

• General models like DeepSeek are essentially "writing an article word by word":

even if you only ask it to make the simplest "yes/no" judgment, in the background it still has to push out one word at a time, forcibly going through a long generation process, with latency starting at seconds

• Jev is officially positioned as a "System 1 (fast decision)" model, and fundamentally it doesn't write at all:

it completely abandons word-by-word output, and at the underlying level directly produces results in parallel all at once. It doesn't output half a sentence of nonsense, and within 70 to 200 milliseconds directly throws out the final answer the code needs (right/wrong, score, classification)

demo reference @elvissun Github open source:

I suggest everyone try JEV, the more you use it the more awesome it feels.....

Show the original post in its source language ▾

完全睡不着了....这个视频让你完全看懂JEV的恐怖能力

我实际演示了一下,用 JEV 和 DeepSeek 做同一个任务:从当天的海量实时新闻流里,为 15 个品牌快速匹配有没有适合借势的公关热点,并打上结构化意图分类标签

结果是:28 秒内,Jev 狂刷完了整整 428 条数据,并完成了全部的目标分解与分类;而同一时间跑在同样任务上的 DeepSeek V4.1-flash,才刚刚完成 6/428 条

速度被拉开了几十倍,答案甚至在你读完第一行字之前就已经返回了....

为什么会产生这么恐怖的差距?底层逻辑是:

• DeepSeek 这种通用模型本质上是在“逐字写文章”:

哪怕你只让它做个最简单的“是/否”判断,它在后台也必须一个词一个词往外推,硬走一遍漫长的生成流程,延迟按秒起步

• Jev 官方定位是“System 1(快决策)”模型,从根上就根本不会写字:

它彻底抛弃了逐字吐词,底层直接一次性并行出结果。不输出半句废话,70 到 200 毫秒内直接甩出代码需要的最终答案(对/错、打分、分类)

demo参考@elvissun Github开源:

建议大家试试JEV,越用越觉得牛逼.....

The post above is a machine translation from zh; the untranslated text is in the fold-out.

Quoted post

@SUOHA_AI45.4K views
source

很多人没看懂爆火的JEV是什么? 所以我做了一个 50 秒的演示视频,带大家把海外刷屏的 JEV 以及它背后的底层架构看透👇(见下方视频) JEV 是前 OpenAI、参与 ChatGPT / RLHF 的 @CompleteSkeptic(Diogo Almeida)创办 @typesafeai 后的第一款模型 他在 OpenAI 时发现了一个致命矛盾:

What the author linked

Engagement when collected

Views4.3K
Likes15
Bookmarks44
Reposts5
Replies2
Quotes1

Numbers are a snapshot taken from X when the case was added to the library (schema v1, collected 2026-09-19); they will not match today.

Where this case fits

Filed under coding & developer tools. In the pattern Jev is built for, the model answers a bounded question per step — and ordinary code acts on the answer, because the answer is already a value rather than a paragraph. Other posts in the same family are on the coding & developer tools page.

Related Jev cases

Keep browsing: all 1173 Jev cases · more from @SUOHA_AI · builders · what Jev is

Last updated: 2026-09-22 · sources & corrections · every card links to its author's original post