| ▲ | the__alchemist 5 hours ago | |||||||||||||||||||||||||||||||||||||||||||
Hey! I think it's confusing because there is a mix of three components:
All 3 of these are a one-dimensional balance of price/speed, and capability (Loose terms). The confusion is in how these overlap, how they're announced/marketed etc. So you go from 1 dimensions to 3; you can visualize it as a box. For a given task, how do you choose where in this box you select? Which regions are your favorite? Can you map each region of this 3D space to specific tasks? Label them with intuitive names?Given the operations of the model are opaque, can you see how someone (most people?) might be confused? | ||||||||||||||||||||||||||||||||||||||||||||
| ▲ | mediaman 5 hours ago | parent | next [-] | |||||||||||||||||||||||||||||||||||||||||||
But what's the ask? This is the cleanest way I see of them doing it. I see a ton of criticism and not a single person coming up with anything better, unless it's to take away options, like removing effort level. What about buying Intel CPUs? A car? Electrical components? If you're not just using this at a consumer level to ask about cooking recipes (and if that's your use case, you really don't care about API pricing, or any of this, and can just use the default), and are using it professionally, then this seems like a low bar of effort to understand what you're buying. I do grant you the relationship between model and effort level has an unclear relationship, but there are also tradeoffs in most complex technical products that are not always clear; this is exacerbated by the fact that this product is stochastic. Why are engineers using this as a professional tool expecting this to be bought like a consumer gadget and then blaming the maker? | ||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||
| ▲ | Y_Y 5 hours ago | parent | prev | next [-] | |||||||||||||||||||||||||||||||||||||||||||
Effort (as it's used in the context, how many "thinking" tokens to burn) is still a free variable. It's not always shown to the end user but you can set it independently for any of these models. After that you just have model "strength" and version number. But of course strength is only comparable at equal version number and the two axes are almost parallel. Anthropic also does this, perhaps to a lesser extent. | ||||||||||||||||||||||||||||||||||||||||||||
| ▲ | 5 hours ago | parent | prev [-] | |||||||||||||||||||||||||||||||||||||||||||
| [deleted] | ||||||||||||||||||||||||||||||||||||||||||||