It's quite fast if you use it at ~4 AM in the US. There's definitely a cycle in time. Putting things in a queue to run while you sleep is a good work around.
It's about using the right tool for the right job. GPT-4 is an incredibly versatile generalist tool and a fantastic jack of all trades. However, this comes with some drawbacks. While saying it 'sucks' might be an exaggeration, I generally concur with the point you're making.
It's no exaggeration that it sucks for certain use cases where you would expect and can achieve near-realtime response, and that's fine because it's not built for that use case. I'm responding to someone saying it's always best if you can afford it
Yea 3.5 is more than good enough for a whole slew of tasks (especially code), and it's ridiculously fast. I rarely find the need to use 4 but certainly if there was a usecase it was significantly better at that mattered to me, I would.
And far more expensive than ChatGPT via API, so it makes sense to use ChatGPT3.5, or the locally run equivalents once they get as good, as much as possible.