3 ms·
Just use what works for you. E.g. i'm very outspoken about my preferences for open llm practices like executed by Meta and Deepseek. I'm very aware of the regu
by PeterStuer 2y ago
Just use what works for you.
E.g. i'm very outspoken about my preferences for open llm practices like executed by Meta and Deepseek. I'm very aware of the regulatory caption and pulling up the ladder tactics by the "AI safety" lobby.
However. In my own operations I do still rely on OpenAI because it works better than what I tried so far for my use case.
That said, when I can find an open model based SaaS operator that serves my needs as well without major change investment, I will switch.
- hnlurker22 2y agoWhy not vibe-code it using OpenAI
- PeterStuer 2y agoI'm not talking about me developing the applications, but about using LLM services inside the products in operation. For my "vibe coding" I've been using OpenAI, Grok and Deepseek if using small method generation, documentation shortcuts, library discovery and debugging counts as such.
- nautilus12 2y agoJust call it hacking, we don't need new names for coding without any forethought.
- hnlurker22 2y agoWho put you in charge of naming?