Live data from Hacker News

Please don't discontinue Gemini 2.5 Flash

discuss.ai.google.dev

11–20 of 93 posts

Re: Please don't discontinue Gemini 2.5 Flash

#13
Agree with the observation others have made. The only true solve if a specific model version is critical to your application or workflow, you need to host the model yourself so you have control over it. You don't want to be stuck getting rug-pulled by a model provider.

And as another commenter pointed out - in particular for Google of all companies - expect that the rug pull can and will happen. They're not known for keep anything around for very long.

Re: Please don't discontinue Gemini 2.5 Flash

#14

UGH why are they killing this model? This is one of the best models you can use in an API for a large swath of tasks. It's kind of the perfect trifecta of fast, cheap, and smart enough. Why does Google constantly kill off good things?

because they keep these models loaded, and they can't just arbitrarily load up whatever models you want. but it's more likely just a business case: they need you buying higher tier model output. They know whose doing what, so someone needs their 3Q bonus.

I was going to reply that Anthropic, which supposedly is the most capacity constrained of the leading AI labs, still provides access to models as old as Opus 3.

But then I realized Opus 3 is an outlier, and Anthropic has removed access to relatively more recent models. https://platform.claude.com/docs/en/about-claude/model-depre...

I wonder what the deal is with Opus 3.

Re: Please don't discontinue Gemini 2.5 Flash

#15
post #9

I love how there is a "Please do not discontinue gemini-2.0-flash[-lite], 2.5 is NOT an equivalent" from Feb 20th. Getting too attached to models is a smell.

That's like saying 'getting attached to locked dependencies for your app is a smell'.

But this could be framed as 'getting attached to an API revision when a new one is available'...

I can see it both ways, tbh.

Re: Please don't discontinue Gemini 2.5 Flash

#16
post #15
post #9

I love how there is a "Please do not discontinue gemini-2.0-flash[-lite], 2.5 is NOT an equivalent" from Feb 20th. Getting too attached to models is a smell.

That's like saying 'getting attached to locked dependencies for your app is a smell'. But this could be framed as 'getting attached to an API revision when a new one is available'... I can see it both ways, tbh.

[deleted]

Re: Please don't discontinue Gemini 2.5 Flash

#17
post #9

I love how there is a "Please do not discontinue gemini-2.0-flash[-lite], 2.5 is NOT an equivalent" from Feb 20th. Getting too attached to models is a smell.

In the post the issue is performance. Are you saying that getting too attached to performance is a smell? That sounds very odd.

It's not because a model performs better in some applications (often by fine-tuning to get better scores at specific tests) that it is better across the board or that we have to believe the company releasing the model with a high number 3 > 2 so that it is commonly accepted as better.

Pushing the reasonnning further: f you need an Opus level performance then not accepting GPT 3 isn't a smell.

Re: Please don't discontinue Gemini 2.5 Flash

#19
post #9

I love how there is a "Please do not discontinue gemini-2.0-flash[-lite], 2.5 is NOT an equivalent" from Feb 20th. Getting too attached to models is a smell.

I built some BigQuery workflows on 2.0 and 2.5 flash lite that are something like 6x more expensive with 3.1 flash lite.

I tried 3 flash for months and it didn’t work using Googles own vertexai integration because it’s been in preview mode for months.

Not wanting to pay significantly more and do a bunch of rework isn’t a smell.

They left a large gap in their new pricing vs the prior generation, and if you had a working use case that sucks. The model is >99% reliable for my use case so there’s nothing to gain from a smarter model.

Post reply on HN