Jev is such a different approach where you have to be specific about what you want and which options are open. Really interesting how those things evolve in usable features for people.

Also with this example the speed of new launches based on a launch is just incredible.

▲

chvid 6 hours ago | parent | next [-]

"... such a different approach where you have to be specific about what you want and which options are open" --- back to where we started ...

	▲	bsenftner 5 hours ago \| parent \| next [-]
		Which few to none seem to have understood why, and they do not incorporate, composing their requests with implied information any AI must guess what the hell this request is talking about. Look for and replace implied information with explicit information (that does not have to be detailed, just the correct non-casual language loaded with implied context.)
	▲	lucfranken 6 hours ago \| parent \| prev [-]
		Not sure on that, maybe the options to choose from will be generated and curated. Same as we do with tagging datasets for images. Might be wildly successful for real world decisions.

▲

adroitboss 2 hours ago | parent | prev [-]

I think this is because the approach isn't that different the mentality was. Encoder only classification isn't new. General encoder only classification isn't new. Gliner2 was something similar for parsing. But what they did is provide a new way to look at a sub-class of problems. They opened a lot of people's eyes, including my own, to the demand for applications in this subsection of the market.

But once you have the mental shift, everything else has been done before. So it's not super hard to build something similar for your own use case.