Been hoping for something in this space. Jev-like decision models on Qwen3.5 could really simplify some of our internal routing logic.
mugul•16m ago
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•15m ago
Yeah same. Got access to their API and then realised I don’t really have an immediate use case
lucrbvi•9m ago
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.
monkeydust•10m ago
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•4m ago
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"
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.
dunlin•22m ago