Using an open model feels surprisingly good
matthewsaltz.com
Using an open model feels surprisingly good
1–10 of 157 posts
Re: Using an open model feels surprisingly good
#2Re: Using an open model feels surprisingly good
#3It surprises me that this concept took as long as it did to gain traction in… hacker news. 15 years ago folks here were compiling kernels and gentoo distros. Lately it’s been “you should just pay the man, it’s cheaper than running these things yourself”
Re: Using an open model feels surprisingly good
#4Re: Using an open model feels surprisingly good
#5For example, if you modify things at the level of small functions, open models seem to perform just as wel
Re: Using an open model feels surprisingly good
#6Now I can't wait for someone to distill K3 into a Qwen 3.6 27b or Poolside S 2.1 sized models for a proper fast local Composer 2.5 replacement.
Re: Using an open model feels surprisingly good
#7It surprises me that this concept took as long as it did to gain traction in… hacker news. 15 years ago folks here were compiling kernels and gentoo distros. Lately it’s been “you should just pay the man, it’s cheaper than running these things yourself”
Re: Using an open model feels surprisingly good
#8The TTFT and tok/s are much higher on the small model so that makes it competitive for a bunch of things. It feels like what old Sonnet used to by the end of last year which is honestly damned good.
Re: Using an open model feels surprisingly good
#9What would be useful is a cost metric. I'm curious how much I'd be willing to spend as a premium to not have those companies piping my conversations directly to the NSA. Maybe only some conversations? Claude and OpenAI are heavily subsidized, by all accounts, so Kimi K3 on a private endpoint might end up costing more or less - that's what I want to know.