Regarding the localness, are you optimizing or targeting users that prefer only local inference? The part about API keys at the end makes me wonder if there's any practical difference outside of lower local resource requirements and access to private models on the clound.
Do you recommend or force that people use any specific languages or frameworks that dyad is optimized to render or iterate on locally?
I definitely want to support users who want to use cloud inference or local inference because you do need a pretty beefy machine to run the top open source models.
Right now Dyad supports React (vite), but i'm working on supporting more frameworks in the future! (other languages is probably further off)
I think practically, the nice part with Dyad is that all the code is on your computer, so if you want to switch back and forth with Cursor/VS Code, it's seamless.
Comments
Very nice!
Regarding the localness, are you optimizing or targeting users that prefer only local inference? The part about API keys at the end makes me wonder if there's any practical difference outside of lower local resource requirements and access to private models on the clound.
Do you recommend or force that people use any specific languages or frameworks that dyad is optimized to render or iterate on locally?
thank you!
I definitely want to support users who want to use cloud inference or local inference because you do need a pretty beefy machine to run the top open source models.
Right now Dyad supports React (vite), but i'm working on supporting more frameworks in the future! (other languages is probably further off)
I think practically, the nice part with Dyad is that all the code is on your computer, so if you want to switch back and forth with Cursor/VS Code, it's seamless.