Leaving aside the technical issues, in my opinion, this is suitable for large companies with large queries. If the goal is simplification, instead of calling your API, large companies will create a similar version themselves, reducing API costs and eliminating the need to contact you. Request from the company -> your server -> your server reads and processes -> returns the result. Therefore, they would rather do it themselves for peace of mind.
This language is used for isolation at the language level and trusts the code written by the library developer. If absolutely necessary, I think environment isolation should still be used. What do you think of this approach ?
Many people on various platforms say that AI is about to replace developers, but I find that most people selling courses or APIs say the same thing. I think the layoffs are due to the economic downturn; they talk about AI to sound cool.
I once heard someone create a QR code scanner to retrieve gigabytes of data, but the biggest problem is that cameras aren't powerful enough to handle it all. Essentially, the QR code needs to be downloaded to the device for loading; relying on the camera to retrieve it is very difficult. Am I wrong about this project? What's your solution?
I think one feature that would make dari-docs significantly more practical for real-world pipelines is a robust, built-in bidirectional converter between Markdown and HTML
What happens if the model continuously hallucinates or provides wrong answers until the user give up ? Will the AI trust those wrong answers and save it ?
It's inevitable, in my opinion; the current trend is to use tools with modern, cross-platform syntax for easier development. Java and XML are becoming outdated and frustrating, at least for me.
The cost of tokens used by AI in many fields is even greater than the cost of human services; people are experiencing FOMO, but once the wave passes, the market will stabilize.