typesafes

10 stories and discussions about typesafes, aggregated from every source we track.

1.

TypeSafe's Jev is a genuine breakthrough – snap judgments with calibrated probabilities instead of generated text. My bet is OpenAI is already figuring out how to copy it, and then embed it inside its own models where…

322 points•JohnBerryman•9 days ago•223 comments•
2.

kicking the tires on jev with 2048. GitHub Gist: instantly share code, notes, and snippets.

19 points•ndyg•12 days ago•2 comments
3.

For the last few weeks my timeline has been nothing but Jev. TypeSafe AI shipped it, and within days...

5 points•programmerraja•8 days ago•0 comments
4.

TypeSafe's Jev is pitched at exactly the decisions that sit around a phone call. We put it on three real jobs against 17 models: it is 1.7 to 3.3 times faster everywhere, level with the best on judging and extraction,…

3 points•xan_ps007•5 days ago•0 comments•
5.

Benchmark of TypeSafe's Jev against Sonnet 5, GPT-5 nano and local LLMs on 770 Reddit AITA verdicts: Brier scores, latency and cost - dchristopoulos/jev-aita

3 points•dchristopoulos•7 days ago•0 comments•
6.

TypeSafe's Jev against four shipped prompt-injection detectors on 7,803 labeled messages and 296 conversations. It wins the curated benchmark and the newest attack set, loses two older ones, and its probabilities track…

3 points•ramoz•10 days ago•0 comments•
7.
2 points•yawnxyz•1 day ago•0 comments•
8.

Open-weight GLiNER2.5-Decide in MLX Swift versus TypeSafe’s hosted Jev: what each offers, what the published benchmark compared, and local measurements: 7.6 ms per request at 0.85 GB with INT8.

2 points•aufklarer•4 days ago•0 comments•
9.

TypeSafe's Jev answers a closed question with a fixed answer type plus a number saying how sure it is. We moved our four decisions over to it. What worked, what didn't, and one thing we didn't expect.

2 points•aozisik•9 days ago•0 comments•
10.
1 points•sts153•11 days ago•0 comments•

Related topics