- 152comments
- 9comments
- 38comments
- 370comments
- 15comments
- 11comments
- 100comments
- —discuss
- 28comments
- 120comments
- 82comments
- 227comments
- 3comments
- 59comments
- 47comments
- 1comments
- 40comments
- 382comments
- 625comments
- 162comments
- 152comments
- 31comments
- 416comments
- 399comments
- 18comments
- —discuss
- 57comments
- 25comments
- 129comments
- 51comments
«The honest table». Right. Not interested in reading what you didn’t write.
Yeah, when I saw that I immediately rolled my eyes and closed that tab.
good to have a quick overview, though I am missing some kind of depth, like
Sure, but... MLX native runtime have a lot of advantages right? and they are not necessarily more complicated like eg ollama. It's worth to mention them, too.
Coming to the next missing part: use cases.
Running it locally competes with dozens of freely available chat bots. And for most simple parts, seriously, you don't need that sophisticated payed AI service. But then: how do local model's perform exactly here: let's start with coding, image generation and more? Like stuff that I probably really want to run locally.
Entire article is vibeslopped
Vibe slop article advertising a product
Whats the best coding model that fits on 16GB unified memory these days?
clearly AI written (aka "slop"), stopped reading after a few paragraphs
This is old, lm studio support has dropped quite a bit.
As of July the best seemed to be
* nativ
* omlx
* mtplx