26 points tosh 51 minutes ago 12 comments
dunlin 23 minutes ago | parent
Been hoping for something in this space. Jev-like decision models on Qwen3.5 could really simplify some of our internal routing logic.
mugul 18 minutes ago | parent
Quite impressed by the energy people are putting into making OSS Jev-like models.
I understand the hype but I wonder: what are the use cases for this kind of model? Could it be used in the context of coding agents, or is it more relevant in totally different situations?
Havoc 16 minutes ago | parent
Yeah same. Got access to their API and then realised I don’t really have an immediate use case
lucrbvi 11 minutes ago | parent
You should call Jev-like models when you give it a JSON-like structure to produce, it is useful when you need _some_ intelligence in your code.
saejox 3 minutes ago | parent
To develop a smart ai system for my 2d roguelike platformer?
game has way too many moving system for classic state-machine ai + i cant spare the time to develop it.
its low latency entices me.
vidarh 2 minutes ago | parent
Consider every situation where you "force" an LLM to output only a choice / category, or a set of them. If you have workflows like that, you're now being promised significant cost- and latency reduction.
For coding agents it'd only be useful in a subset of situations. E.g. you could imagine using one to classify bash tool calls into safe and unsafe for example.
monkeydust 11 minutes ago | parent
Bit of a Jev explosion going on. Is it because it's taking us back to a simpler time we understand better? Classification models have been around for a while.
toasty228 5 minutes ago | parent
It's because everyone wants their 15 minutes of fame so every single time something shiny gets out all the NPCs are asking astra/fable: "can you create a copy of this, make no mistake"
webprofusion 5 minutes ago | parent
nullbio 5 minutes ago | parent
I think a great use case for these will be when they have large context windows and are able to enforce styling rules for frontend development, and component creation rules for react. You can then ditch the styles guides and styling skills and create a decision tree for enforcing styling, so that you can't run into drift issues or duplication issues. That's where I'm wasting most of my time right now, constantly correcting all of the UX/UI issues that are created for every single feature.