Recent submissions

Comment · 1 month ago
Cool
Comment · 3 months ago
It's hard to keep track of all those launches, I agree. I would separate 2 usages of LLMs: - LLM is integrated into a workflow/app for a classification or whatever job: scoring outputs (evals, KPIs) and choosing a fit between quality and cost is enough - LLM is used as a tool you interact with (like coding or research): here is where you have to know your brushes. As humans we get used very quickly by the model personality, the format of output, the way it "thinks" and interacts.
Comment · 3 months ago
a French human doing its best to sound punchy in English :)
Comment · 3 months ago
Yes. orchestrator > smart router
Comment · 3 months ago
Sounds like an orchestrator for me ratter than a router
Comment · 3 months ago
Agree
Comment · 3 months ago
We tried different things: heuristic, TF-IDF and LLMs. I voluntarily didn't talk about the tech because it doesn't fix the problems mentioned by switching models on the fly.
Comment · 3 months ago
100% agree. MoE is the perfect example: reducing FLOPs while keeping intelligence
Comment · 3 months ago
All inference providers (labs and neoclouds like TogetherAI or Fireworks) are incentivized to be efficient to be more competitive. For example MoE reduces compute without reducing output quality. I would not be surprised if they end up implementing some kind of internal routing at some point.
Comment · 3 months ago
Cheers, good luck!
Comment · 3 months ago
Could be. In that case many routers are concerned as they all have more or less the same category buckets.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton