- 119comments
- 20comments
- 4comments
- 29comments
- 364comments
- 9comments
- 15comments
- 97comments
- 21comments
- 119comments
- 220comments
- 56comments
- 11comments
- 34comments
- 37comments
- 379comments
- 615comments
- 2comments
- 159comments
- 145comments
- 30comments
- 412comments
- 386comments
- 18comments
- 57comments
- 25comments
- 17comments
- 49comments
- 128comments
- 673comments
«The honest table». Right. Not interested in reading what you didn’t write.
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 As of last month the b st seemed to be
* nativ
* omlx
* mtplx