|
|
|
|
|
|
by awayto
1082 days ago
|
|
|
Why would I use this instead of some minimal implementation of the official OpenAI packages? Looking at the chatgpt.js file in the repo, a great deal of the code revolves around manipulating UI elements. What does any of this have to do with interacting with an API, and why would I use your UI, baked into this script, outside of something I control myself? Then, the Usage section shows a few commands, completely unrelated to any UI elements. I'm not sold on this; seems like a wrapper around something that is much simpler in practice. > Who has time for docs? Perhaps you could... I dunno, use an AI or something to generate those for you? |
|
|
> Why would I use this instead of some minimal implementation of the official OpenAI packages?
If you're looking to use API, you wouldn't (this is client-side not server-side library)
> Looking at the chatgpt.js file in the repo, a great deal of the code revolves around manipulating UI elements.
Yes that's what this library is for
> What does any of this have to do with interacting with an API
Nothing... (who said it interacts with API?)
> why would I use your UI, baked into this script, outside of something I control myself?
The same reason authors of award-winning apps that use chatgpt.js do... to write less code (literally anyone uses libraries). Why do you need to control a library's code?
> I'm not sold on this; seems like a wrapper around something that is much simpler in practice.
It doesn't wrap anything it's original functions...
> "Who has time for docs?" Perhaps you could... I dunno, use an AI or something to generate [docs] for you?
A human wrote them already @ https://github.com/kudoai/chatgpt.js/blob/main/docs/userguid... the quote refers to users not me