25 karma · joined September 23, 2019
I guess familiarity ultimately determines much of our font preference
Honestly, this is my first macOS app and I'm a bit out of ideas when it comes to performance. If anyone has tehcnical knowledge about SwiftUI and how I could improve performance, please do contact me ! (contact@machato.app)
My experience has been that the SwiftUI Profiler shows that almost all processor time is spent deep inside SwiftUI/AppKit primitives, despite there being close to no updates to view properties.
I'm glad HN is enjoying the app despite those issues. I promise I'm doing my best !
>> servings: 2|4|8
Add @milk{1/2*%cup} and mix until smooth. -- Multiply by serving size
Add @milk{1|2|3%cup} and mix until smooth. -- Specific quantity per serving size
I'm curious as to why this appears in your ToS, as this is quite a deterrent for many.
My experience has been that using it this way is fairly inexpensive. You can track your expenses in real time and put spending limits on OpenAI's dashboard, so you don't get a bad surprise at the end of the month.
- Noted ! This shouldn't be too hard to implement.
- This is an important feature, I'm looking to implement it in the very near future.
- I had this happen a few times. I'll try to troubleshoot the issue. In the meantime, I found that resizing the window fixed the issue.
- Yup ! I've added it to the to-do list.
- What kind of format would you find useful ?
I'm happy you're enjoying the app.
As for audio integration, this in not on the to-do list, as I am looking to keep the client lightweight.
As for the default temperature, 0.0 is actually a bug ! I'll definitely fix that in the next release. The default intended value is 1.0. The API reference [1] describes what the temperature parameter does in more detail.
While doing some testing, I also noticed that the app disables streamed responses by default. Make sure to check the appropriate checkbox in the settings to get token-per-token answers !
[1] https://platform.openai.com/docs/api-reference/chat/create
Admittedly, the API doesn't provide nearly as many features as ChatGPT Plus does. To each their own !
- ChatGPT Plus is crazy expensive, and the free tier is often down. I found it especially frustrating to not get access to my chat history when ChatGPT's load was high. Since alternative clients go through the API, their are exempt from load balancing.
- A native client is lightweight and doesn't rely on web technologies. This is a matter of personal taste, but I like the look and feel of native apps better than web pages.
- Current native clients are both very new and ill-fitted to my needs (I really like the LaTeX rendering feature and I want to be able to browse my chat history)