Hacker News new | ask | show | jobs
by cyanregiment 1 day ago
There are "Hi" and "Lo" variants of the different models.

Maybe Gemini or ChatGPT is a "Hi" while running a local Mistral 7b is a "Lo" - sometimes you want lo-res technologies. Faster, lighter, does the job.

Find the same with image, video, vision, and so-on.

Probably get away with pretty weak vision models for some basic edge detection, but need "a good one" for things like OCR.

I don't find a ton of competitive difference amongst the "good ones" especially not reflected in the pricing and marketing. IMO there are pretty much just "non-AI" algorithms, "basic AI" that are getting more interesting on-device for some use cases, and "good AI" or what we'd call "frontier models" - which again, not seeing a ton of differentiation on that layer.

2 comments

I concur that there isn't that much difference between the good ones. I'm not really trying to push the limits of what they can do or anything, but I'd say on average I give it tasks about the size of something that would take me a half day to do by hand, and honestly, other than minor quirks in coding style and word choices, they've all basically been "good enough" for what I want. When I tried fable it just wasn't for me because it was basically very expensive overkill. I usually stay on the older models as long as I can just because they're predictable and I care a lot more about predictability and cost than being on the super cutting edge or whatever. (Honestly I'd kind of rather the enthusiasts test it first for the various "new model deleted my database" bugs that seem to pop up.
Yeah definitely good enough for work. I think people only get into trouble going “agentic” and trying to automate je ne sais quoi
I feel like nearly anything done by a "Lo" is better done myself. I use "Hi" for pushing the limits of my expertise.
A good use case for me is automating invoice notes that are all very similar, but change based on details of client and work. Mistral 7b does it fine, instantly.

UX-wise, I don't predict out "ghost text" like Google has been doing, I just preload the input value with the prediction. You can edit as you want. Saves a ton of time.