←back to thread

467 points mraniki | 1 comments | | HN request time: 0.237s | source
Show context
bratao ◴[] No.43534359[source]
From my use case, the Gemini 2.5 is terrible. I have a complex Cython code in a single file (1500 lines) for a Sequence Labeling. Claude and o3 are very good in improving this code and following the commands. The Gemini always try to do unrelated changes. For example, I asked, separately, for small changes such as remove this unused function, or cache the arrays indexes. Every time it completely refactored the code and was obsessed with removing the gil. The output code is always broken, because removing the gil is not easy.
replies(10): >>43534409 #>>43534423 #>>43534434 #>>43534511 #>>43534695 #>>43534743 #>>43535378 #>>43536361 #>>43536527 #>>43536933 #
redog ◴[] No.43534511[source]
For me I had to upload the library's current documentation to it because it was using outdated references and changing everything that was working in the code to broken and not focusing on the parts I was trying to build upon.
replies(2): >>43534560 #>>43535477 #
Jcampuzano2 ◴[] No.43535477[source]
If you don't mind me asking how do you go about this?

I hear people commonly mention doing this but I can't imagine people are manually adding every page of the docs for libraries or frameworks they're using since unfortunately most are not in one single tidy page easy to copy paste.

replies(3): >>43535857 #>>43538489 #>>43540602 #
1. dr_kiszonka ◴[] No.43535857[source]
If you have access to the documentation source, you can concatenate all files into one. Some software also has docs downloadable as PDF.