Earlier quoted context omitted.
Ok, so saying "Implement feature X" leads to a ton of comments. How do you rewrite that comment to not include "don't write comments" while making the output not containing comments? "Write only source code, no plain text with special characters in the beginning of the line" or what are you suggesting here in practical terms?
"Implement feature X, and as you do, insert only minimal and absolutely necessary comments that explain why something is being done, not what is being done."
Gemini 2.5 Pro Preview
141–150 of 728 posts
Re: Gemini 2.5 Pro Preview
#142Earlier quoted context omitted.
No, it's just bad. I've been writing a lot of Python code past two days with Gemini 2.5 Pro Preview, and all of its code was like: ```python def whatever(): --- SECTION ONE OF THE CODE --- ... --- SECTION TWO OF THE CODE --- try: [some "dangerous" code] except Exception as e: logging.error(f"Failed to save files to {output_path}: {e}") # Decide whether to raise the error or just warn # raise IOError(f"Failed to save…
It's certainly annoying, but you can try following up with "can you please remove superfluous comments? In particular, if a comment doesn't add anything to the understanding of the code, it doesn't deserve to be there".
Just end your prompt with "no code comments"
Re: Gemini 2.5 Pro Preview
#143Interestingly, when compering benchmarks of Experimental 03-25 [1] and Experimental 05-06 [2] it seems the new version scores slightly lower in everything except on LiveCodeBench. [1] https://storage.googleapis.com/model-cards/documents/gemini-... [2] https://deepmind.google/technologies/gemini/
Fair enough, one could say, as these were all labeled as preview or experimental. Still, considering that the new model is slightly worse across the board in benchmarks (except for LiveCodeBench), it would have been nice to have the option to stick with the older version. Not everyone is using these models for coding.
Re: Gemini 2.5 Pro Preview
#144Is there anything like Claude code for other models such as gemini?
Re: Gemini 2.5 Pro Preview
#145Earlier quoted context omitted.
I'm actually very happy with everything in Claude code, eg the CLI so im really just curious to try other models
Same! I prefer the CLI, way easier when I’m connected via ssh from another network somewhere.
But with my app: you can install the host anywhere and connect to it securely (via SSH forwarding or private VPN or what have you) so that workflow definitely still works!
Re: Gemini 2.5 Pro Preview
#146I don't know if I'm doing something wrong, but every time I ask gemini 2.5 for code it outputs SO MANY comments. An exaggerated amount of comments. Sections comments, step comments, block comments, inline comments, all the gang.
Models use comments to think, asking to remove will affect code quality.
Re: Gemini 2.5 Pro Preview
#147I don't know if I'm doing something wrong, but every time I ask gemini 2.5 for code it outputs SO MANY comments. An exaggerated amount of comments. Sections comments, step comments, block comments, inline comments, all the gang.
Re: Gemini 2.5 Pro Preview
#148Earlier quoted context omitted.
I've tried this, aggressively and it still does it for me. I gave up.
I tried this as well. I'm interfacing with Gemini 2.5 using Cursor and I have rules to to limit the comments. It still ends up over-commenting.
Re: Gemini 2.5 Pro Preview
#149I'm totally lost again! If I use Gemini on the website (gemini.google.com), am I using 2.5 Pro IO edition, or am I using the old one?
Re: Gemini 2.5 Pro Preview
#150Earlier quoted context omitted.
I've found that heavily commented code can be better for the LLM to read later, so it pulls in explanatory comments into context at the same time as reading code, similar to pulling in @docs, so maybe it's doing that on purpose?
No, it's just bad. I've been writing a lot of Python code past two days with Gemini 2.5 Pro Preview, and all of its code was like: ```python def whatever(): --- SECTION ONE OF THE CODE --- ... --- SECTION TWO OF THE CODE --- try: [some "dangerous" code] except Exception as e: logging.error(f"Failed to save files to {output_path}: {e}") # Decide whether to raise the error or just warn # raise IOError(f"Failed to save…