I would very much like not to have to download 22 GB for some inference capability that is way worse than API calls both in terms of quality and speed.
I would rather pay money than seeing this thing running in my browser that only prints 5 tps on high-end consumer hardware.
Fair, but actually you'd surely want your choice of those three, right?
And what's being discussed here is what the better implementation of option 3 is.
My point is that if you're going with one of the possible implementations of option 3, then 22GB per browser is objectively a lot better than 22GB per website.
Well, Musk v OpenAI kicks off in one week from now with the objective of forcing them back to their roots. A jury will be deciding whether a nonprofit accepting $50m - $100m of donations and then discarding their mission for an IPO is OK or not. Should be interesting.
It can write (some) code that works. Just roughly guessing from my use, but I think of it as being a bit like ChatGPT circa-2024 in terms of capability & speed.
Disappointing if you compare it to anything else from 2026, but fairly impressive for something that can run locally at an OK speed.
He might not specifically lie, but puts such a negative spin on anything Elon-related that the overall result is essentially a lie.