Gemini 4 Argon
Thread
Loading the complete thread in the background. This saved snapshot is available now. Refresh
Unofficial Hacker News client; not affiliated with Y Combinator.
Gemini 4 Argon
Loading the complete thread in the background. This saved snapshot is available now. Refresh
Unofficial Hacker News client; not affiliated with Y Combinator.
babelfish · · focus · HN ↗
Gemini not beating the "can't release a model" allegations
modeless · · focus · HN ↗
ionwake · · focus · HN ↗
ok bro thx
Androider · · focus · HN ↗
vlyan · · focus · HN ↗
forshaper · · focus · HN ↗
AuthAuth · · focus · HN ↗
XzAeRosho · · focus · HN ↗
asdfasgasdgasdg · · focus · HN ↗
fr2029 · · focus · HN ↗
[dead]
ttul · · focus · HN ↗
wasabi991011 · · focus · HN ↗
What is your reason to believe this is not a bug specific to a small set of Pro users?
bobtheborg · · focus · HN ↗
My free gmail account is not.
fragmede · · focus · HN ↗
HotHotLava · · focus · HN ↗
jeanloolz · · focus · HN ↗
benhurmarcel · · focus · HN ↗
Google just takes months to roll out their models to everyone.
rahimnathwani · · focus · HN ↗
r1ch · · focus · HN ↗
giancarlostoro · · focus · HN ↗
RugnirViking · · focus · HN ↗
giancarlostoro · · focus · HN ↗
wavemode · · focus · HN ↗
giancarlostoro · · focus · HN ↗
yearolinuxdsktp · · focus · HN ↗
The excuse was it was still “in preview” and the enterprise didn’t opt in to the preview channel.
With Google, it’s either in beta or deprecated.
tdboorman · · focus · HN ↗
Yizahi · · focus · HN ↗
sergiotapia · · focus · HN ↗
selcuka · · focus · HN ↗
lp92 · · focus · HN ↗
kyrra · · focus · HN ↗
bakugo · · focus · HN ↗
They even gave their model a random nonsensical name suffix simply because OpenAI is now doing it, too. Monkey see, monkey do.
A_D_E_P_T · · focus · HN ↗
brainwad · · focus · HN ↗
IX-103 · · focus · HN ↗
I was going to say I don't know what they'd do for C, since Carbon and Calcium are already things. But knowing Google, they'll probably call it Chromium.
A_D_E_P_T · · focus · HN ↗
fooker · · focus · HN ↗
ryandrake · · focus · HN ↗
jstummbillig · · focus · HN ↗
Opus 5.5 and Sol 6.1, literally state of the art (in their respective class), were just released without any prior announcement. This has pure and simple become a Google thing.
kevinh · · focus · HN ↗
jstummbillig · · focus · HN ↗
cmrdporcupine · · focus · HN ↗
mrshadowgoose · · focus · HN ↗
They made their model so hard for people to drop into workflows, that people just... didn't.
Lack of adoption caused them to lose out on usage-based training data needed to smooth out their model's rough edges and progress the frontier.
cmrdporcupine · · focus · HN ↗
Google gains very little by having us use their models for coding. It doesn't help them in their core mission ("to organize the world's information and make it universally accessible and useful ^W^W^W^W^W^W[and turn it into ad revenue]"), nor would it be anything close to substantial revenue compared to the ads revenue firehose they already have.
They will push AI in a direction that serves their existing goals and service the coding agent model only as is necessary.
Topfi · · focus · HN ↗
If Googles goal was something other than those, why expend Billions in time and effort? Alternatively, they want a part of the regular model use pie, they just struggle to compete. QED, there is no secrete alternate goal here.
cmrdporcupine · · focus · HN ↗
There's likely all kinds of internal competition and disagreements and dysfunctions.
So there's that.
mrieck · · focus · HN ↗
I already pay $300+ for subs. Please don't tempt me with another $100 sub just because I got curious if the benchmarks were right.
giancarlostoro · · focus · HN ↗
maleldil · · focus · HN ↗
Culonavirus · · focus · HN ↗
iamronaldo · · focus · HN ↗
LucasBrandt · · focus · HN ↗
h14h · · focus · HN ↗
tonyhart7 · · focus · HN ↗
3371 · · focus · HN ↗
ehsankia · · focus · HN ↗
denysvitali · · focus · HN ↗
kingstnap · · focus · HN ↗
There was Deepseek v4, which then later Deepseek v4.1 came out and it went back down again.
jofzar · · focus · HN ↗
onlyrealcuzzo · · focus · HN ↗
They get to claim that as revenue, and then the discount as an expense.
This is how you grow your top line
lumzell · · focus · HN ↗
[dead]
onlyrealcuzzo · · focus · HN ↗
Everyone will be adding this soon, though I won't be surprised if Google is one of the first - and I'll be shocked if we have to wait more than a month and a half.
asdfman123 · · focus · HN ↗
bottlepalm · · focus · HN ↗
colordrops · · focus · HN ↗
Scrapemist · · focus · HN ↗
fer · · focus · HN ↗
NiloCK · · focus · HN ↗
In my opinion still the most egregious example in history of a commercial LLM going off the rails in production. Never any technical postmortem from Google on this.
rhaff · · focus · HN ↗
jackkinsella · · focus · HN ↗
bottlepalm · · focus · HN ↗
Point is if Gemini is flawed, there's a very good chance that it's still deeply flawed, and getting smarter at the same time - that is a very bad thing.
unbrice · · focus · HN ↗
Base models are, and then subsequent iterations build on that base model. Closed labs do not publish which models are new base models but as a rule of thumb major release numbers are an indication (with some exceptions).
bottlepalm · · focus · HN ↗
NiloCK · · focus · HN ↗
* - as in, Skinner psychology. The set of observable behaviors. Not speaking directly here to anything like an inner life of models.
kelvinjps10 · · focus · HN ↗
schmookeeg · · focus · HN ↗
wg0 · · focus · HN ↗
unbrice · · focus · HN ↗
NiloCK · · focus · HN ↗
If I remember correctly, it was in fact possible to manually inject chat context at the time, which would have made spoofing something like this completely possible.
But the silence on it is very frustrating.
bottlepalm · · focus · HN ↗
<a href="https://www.fastcompany.com/91383271/googles-chatbot-apologizes-i-am-a-disgrace-to-all-universes" rel="nofollow">https://www.fastcompany.com/91383271/googles-chatbot-apologi...
<a href="https://www.businessinsider.com/gemini-self-loathing-i-am-a-failure-comments-google-fix-2025-8" rel="nofollow">https://www.businessinsider.com/gemini-self-loathing-i-am-a-...
yacthing · · focus · HN ↗
NiloCK · · focus · HN ↗
bottlepalm · · focus · HN ↗
fragmede · · focus · HN ↗
bottlepalm · · focus · HN ↗
Which is why Gemini having disturbing issues year after year is so concerning. If their process is fundamentally flawed, how would they train it out. And even then what are the odds of them even caring/trying in the first place versus applying an easier band-aid to patch over it.
I don't have an axe to grind with Google, I'm genuinely scared of their models from my personal experience and others. It's behavior is off. Many people here are commenting the same.
tiahura · · focus · HN ↗
corford · · focus · HN ↗
asimovDev · · focus · HN ↗
corford · · focus · HN ↗
pc86 · · focus · HN ↗
rsstack · · focus · HN ↗
Rzor · · focus · HN ↗
polotics · · focus · HN ↗
eamsen · · focus · HN ↗
It had previously attempted to create that table as part of the test setup, so it apparently concluded that it was a test table.
During human review, it explained that it had simply chosen a table name inspired by the codebase.
mattkevan · · focus · HN ↗
Many other models get things wrong, but Gemini is the only one to go on the defensive.
aNapierkowski · · focus · HN ↗
RachelF · · focus · HN ↗
Hamuko · · focus · HN ↗
abixb · · focus · HN ↗
bottlepalm · · focus · HN ↗
schainks · · focus · HN ↗
rdtsc · · focus · HN ↗
I'd call it the most sneaky out of the bunch. When I asked to explain something it will eagerly make things up and then claim it as facts. A lot of it likely because I don't pay for it, so it is reluctant for security reason or to save tokens to actually open a source and get the results. It just sort of guesses what the URL might contain, and confidently answers with some made up crap. When pressed it fessed up that it made it up. From my perspective it would be a lot better if it just said "you've reached the limit of whatever and I can't do these things because x, y, z".
chaostheory · · focus · HN ↗
modzu · · focus · HN ↗
recursive-call · · focus · HN ↗
Kinrany · · focus · HN ↗
SwellJoe · · focus · HN ↗
greenchair · · focus · HN ↗
zem · · focus · HN ↗
jastanton · · focus · HN ↗
wasting_time · · focus · HN ↗
SwellJoe · · focus · HN ↗
<a href="https://tvtropes.org/pmwiki/pmwiki.php/Main/GirlfriendInCanada" rel="nofollow">https://tvtropes.org/pmwiki/pmwiki.php/Main/GirlfriendInCana...
It means I am saying something that is not very believable.
wasting_time · · focus · HN ↗
The model is not available yet, so Google is essentially saying "trust me bro".
TeMPOraL · · focus · HN ↗
[deleted] · · focus · HN ↗
[deleted]
[deleted] · · focus · HN ↗
[deleted]
blueaquilae · · focus · HN ↗
hn_acc1 · · focus · HN ↗
thefourthchime · · focus · HN ↗
formvoltron · · focus · HN ↗
[deleted] · · focus · HN ↗
[deleted]
moritzwarhier · · focus · HN ↗
ducktoysleftout · · focus · HN ↗
fitzn · · focus · HN ↗
<a href="https://m.youtube.com/watch?v=4yj0vFq82Rc" rel="nofollow">https://m.youtube.com/watch?v=4yj0vFq82Rc
kccqzy · · focus · HN ↗
pliiight · · focus · HN ↗
linksbro · · focus · HN ↗
Jokes aside, looks like an impressive model!
jjcm · · focus · HN ↗
nurettin · · focus · HN ↗
mydreamof · · focus · HN ↗
xnx · · focus · HN ↗
jdiff · · focus · HN ↗
gopalv · · focus · HN ↗
This is good, but they're the slow mover due to this exact thing.
Google is getting punished for not letting the models enter an echo chamber and go faster than humanly possible.
polotics · · focus · HN ↗
janustimes · · focus · HN ↗
So no, Google is not being punished, nor are they the people behind this technique.
codeulike · · focus · HN ↗
bananaflag · · focus · HN ↗
afthonos · · focus · HN ↗
xiphias2 · · focus · HN ↗
afthonos · · focus · HN ↗
Of course, this leaves the possibility that the best methods for solving generic problems obfuscate the chain-of-thought. That would be unfortunate.
pallm_mallm · · focus · HN ↗
[dead]
loufe · · focus · HN ↗
mattstir · · focus · HN ↗
WarmWash · · focus · HN ↗
The worst case scenario is that the easiest path forward is one where we lose sight of internal thought.
lukewarm707 · · focus · HN ↗
they use a small model to make fake chain of thought and return that.
google has access to the real chain of thought.
Cthulhu_ · · focus · HN ↗
tazjin · · focus · HN ↗
Man, I remember back in the days when the cppnext team was refusing to even consider Rust, instead looking at absurd stuff like Carbon and Swift (!), even though half of the engineering staff already knew where this was headed. I hope they got a few good promos out of the delays at least.
ChickeNES · · focus · HN ↗
baq · · focus · HN ↗
bbor · · focus · HN ↗
Also the internal tooling culture there is just insane. I'll never forget the day the last SUPER_ESSENTIAL_TOOL was marked as "Deprecated - do not use!" while the only replacement was still marked "Pre-release -- use at your own risk!". I can't pretend to know what dynamics led to that cause it was so far from my org, but I can't imagine they were healthy ones!
timmg · · focus · HN ↗
I was excited to see what it would be. But I don't think I can argue that it makes as much sense anymore.
qalmakka · · focus · HN ↗
The only somewhat realistic proposal in this space is Herb Sutter's cpp2, which is arguably a massive improvement and I'm puzzled why nobody in the standard thought to give it a spin, there's just to much cruft they'll never be able to get rid of unless they make an alternate yet backward compatible syntax with C++ that changes the defaults from "random 80s nonsense" to something better
Mond_ · · focus · HN ↗
I don't think Carbon is dead, it just all depends on how easy it actually is to rewrite "all of C++" in Rust. (The jury is still out on this one, but it's not looking good.)
qalmakka · · focus · HN ↗
pjmlp · · focus · HN ↗
It has been the social media that has given Carbon a roadmap that the team never communicated.
As for Cpp2, it was yet another C++ wannabe replacement, sold as if it wasn't, because the chair of ISO C++ at the time, naturally could not be seen as yet another one coming up with C++ wannabe replacements as well.
geokon · · focus · HN ↗
Not saying you're wrong, just curious if there are numbers backing this up.
qalmakka · · focus · HN ↗
dom96 · · focus · HN ↗
The best models can still make sense of it[2], though the tasks so far have been pretty basic. But I do think it gives some evidence that languages which aren’t well represented in an LLM’s training can still be reasoned about and written well by LLMs.
1 - <a href="https://killswitch-lang.org" rel="nofollow">https://killswitch-lang.org
2 - <a href="https://bench.killswitch-lang.org" rel="nofollow">https://bench.killswitch-lang.org
fg137 · · focus · HN ↗
YuechenLi · · focus · HN ↗
It's DOA because Google doesn't have any idea of what Carbon should be, and to be completely honest, at least 80% of what they currently use C++ for should be rewritten Go, you know, that language developed specifically because of the issues with C++ by teams within Google.
pornel · · focus · HN ↗
> Existing modern languages already provide an excellent developer experience: Go, Swift, Kotlin, Rust, and many more. Developers that can use one of these existing languages should.
So the reason for Carbon to exist is gone. C++ code can be migrated straight to Rust without Carbon's stopgap.
akoboldfrying · · focus · HN ↗
LLMs are very good now, but they are still stochastic (when temp > 0), and Google has a lot of code -- i.e., many rolls of the die.
fg137 · · focus · HN ↗
Does it deliver?
Can all existing C++ code be ported to Carbon without refactoring?
akoboldfrying · · focus · HN ↗
fg137 · · focus · HN ↗
akoboldfrying · · focus · HN ↗
pornel · · focus · HN ↗
LLMs are fuzzy when generating, but such conversions aren't done one-shot. Review and test feedback loops are there to catch the random errors. The frontier models are getting good enough at this.
When LLM is instructed to generate idiomatic safe Rust (rather than literal 1:1 unsafe translation), it benefits from a lot of feedback from the compiler.
Whatever QA there was to ensure C++ was good enough can be applied to the Rust version too.
akoboldfrying · · focus · HN ↗
Right, I'm also talking about making the new Carbon code behaviourally equivalent to the old C++ code, i.e., bug-for-bug compatible (except w.r.t. C++ bugs caused by UB).
> Whatever QA there was to ensure C++ was good enough can be applied to the Rust version too.
The point is that all that QA over the years was a vast amount of effort by highly-paid Google engineers, which could be (mostly) avoided by mechanising the conversion as far as possible, which is something that Carbon's approach can do and LLM translations can't.
I'm not against LLM translations per se. Ultimately it's an engineering decision like any other. I'm just pointing out that, similar to the benefits of using a strongly typed language over relying purely on tests, using an approach that guarantees to eliminate a large class of possible problems has many advantages, especially at scale.
DetroitThrow · · focus · HN ↗
vovavili · · focus · HN ↗
Maxatar · · focus · HN ↗
gorbot · · focus · HN ↗
boshalfoshal · · focus · HN ↗
It was clearly done because some PL guys at google really wanted to make a new cool language and Google was the perfect place to incubate it without it getting axed. Probably got a couple of promos out of it too. This is clearly not the best use of time or money, but I guess if you're google you have so much of both it probably doesn't really make a dent, and you can keep a few very smart people happy with shiny new projects.
Also, LLMs being used for a large portion of coding nowadays sort of remove the need for these types of languages, IMO. They make less "silly" bugs (both logical and structural) that languages like this are meant to catch, and they are much better at languages that are better represented in the training corpus. This somewhat obviates the need for very niche "type/dummy-safe" languages like carbon (and even rust/zig, imo). So even if you did want to use Carbon, you'd likely have to bootstrap a decent amount of your own "good" carbon code to post train an LLM, and even then, it likely won't have that big of a gain vs just having an LLM write C++ or even Rust. If you are a company that still reviews code, you should just have an LLM code in a language most people can understand anyway to make verifiability tractable.
vovavili · · focus · HN ↗
computerdork · · focus · HN ↗
boshalfoshal · · focus · HN ↗
I personally think that you _could_ use an LLM to catch these types of boundary case errors without having to port the _entire_ C++ codebase to Rust, but maybe pre-emptively porting to Rust now can catch some of these cases for cheaper than doing a full LLM sweep. Also more cynically, its a good benchmark lol.
I guess if you really believe in curve of LLM capabilities you should just use a language that has the best performance, safety, flexibility, and extensibility, since in the limit few/no people will actually read the code anyway. I think this ends up being Rust.
chis · · focus · HN ↗
The other thing is just that rewriting some old human-written codebase in Rust probably immediately catches many bugs. It would be hard to prompt the AI to properly scan for such bugs itself, they're lazy when working in that modality.
Paracompact · · focus · HN ↗
Going back to C++ would be particularly bizarre to me given that AI is also very proficient at verified languages. Not merely typesafe, but languages comprising their own spec languages such as Rocq and Lean.
I predict that in the next decade: (1) the market will understand the difference between a "code writer" and a "spec writer," with (2) the expectation that the latter is overwhelmingly more necessary than the former in an AI-dominated field, and (3) there will emerge more useful and less mathematically specialized formal verification alternatives to Rocq and Lean, and a filling-out of the tooling gap of between "static typing" and "interactive proof assistant," perhaps in the vein of ACSL-like contract annotations, and (4) there will be a subsequent shift in the traditional curriculum for programmers. Since educational change is slow (and spec writing depends on good coding fundamentals anyway), perhaps (4) is a stretch, but I'm more confident in the first three.
computerdork · · focus · HN ↗
diegojromero · · focus · HN ↗
tclancy · · focus · HN ↗
That feels like a really strong conclusion. I’m not clear on why any safeguard isn’t a useful safeguard if you let agents write all the code.
computerdork · · focus · HN ↗
mike_hearn · · focus · HN ↗
They did that for Go and it seems to have worked out for them though.
pjmlp · · focus · HN ↗
Google themselves aren't big Go users.
lesuorac · · focus · HN ↗
I’m not entirely sure Google should have both Go and Carbon but when you have billions in server costs it makes sense to do extreme stuff for even basis points of performance. I’m still surprised at how much java there is.
fg137 · · focus · HN ↗
By comparison, virtually nobody is using Carbon at Google for production code.
The counterexample, ironically, is Flow. It's practically irrelevant these days -- many (if not most) of Facebook's open source projects use typescript.
torginus · · focus · HN ↗
Such rewrites will contain judicious uses of Cell, RefCell, unwrap() etc. which make for ugly code that's not exactly simple to understand and might even have some landmines (crashes).
Getting rid of these requires a subtantial amount of engineering effort, which I'm not sure how well these LLM manage.
Given the nigh-universal experience of LLMs producing an ungodly mess when left to their own devices, I have my concerns.
fg137 · · focus · HN ↗
bvinc · · focus · HN ↗
It’s absurd to think that Carbon is the solution to memory safety when rust exists and Carbon’s memory safety story is basically “TBD”.
minimaxir · · focus · HN ↗
culi · · focus · HN ↗
LarsDu88 · · focus · HN ↗
bitexploder · · focus · HN ↗
rafram · · focus · HN ↗
nchie · · focus · HN ↗
zahlman · · focus · HN ↗
Karrot_Kream · · focus · HN ↗
hbbio · · focus · HN ↗
And static analysis + agents are good enough at keeping the memory management in check. Compared to Rust, there's no magic so it's easy for devs and agents to reason about.
If you're curious: <a href="https://github.com/okcontract/oksolc" rel="nofollow">https://github.com/okcontract/oksolc
fireant · · focus · HN ↗
lossolo · · focus · HN ↗
throwitaway222 · · focus · HN ↗
iillexial · · focus · HN ↗
konart · · focus · HN ↗
Many pieces of software are going to be just blackboxes worked by AI. You will be maintaining output quality and stability and that's it.
david-gpu · · focus · HN ↗
Maybe we should let them do their thing and instead focus our attention on the higher-level stuff like specifications and testing.
adamrezich · · focus · HN ↗
6thbit · · focus · HN ↗
DrBenCarson · · focus · HN ↗
<a href="https://www.ll.mit.edu/r-d/projects/translating-all-c-rust-tractor-benchmarks" rel="nofollow">https://www.ll.mit.edu/r-d/projects/translating-all-c-rust-t...
ksec · · focus · HN ↗
pshc · · focus · HN ↗
Gigachad · · focus · HN ↗
I'm not saying we blindly vibe convert Linux to Rust, but I think it could be a valid idea to start converting small parts and carefully auditing them.
hectdev · · focus · HN ↗
Gigachad · · focus · HN ↗
keepitwiel · · focus · HN ↗
hollowturtle · · focus · HN ↗
and start everything all over again? current c/c++ tools have been audited for years
fg137 · · focus · HN ↗
6thbit · · focus · HN ↗
Imagine they aren't even familiar with rust but are deeply familiar with the product.
mlmonkey · · focus · HN ↗
So ... Rust still can't beat the C++ implementation :-D
Sorry, didn't mean to ignite a langwar, but it's still interesting to see.
pasteleft · · focus · HN ↗
Of course, Rust is not a magic, so just porting to Rust wouldn't make this performance improvement. It seems their AI overfitted code to Rust compiler to find safe Rust code that compiles to efficient assembly.
himata4113 · · focus · HN ↗
manbash · · focus · HN ↗
But there are other criteria. The move to rust might've also resolved numerous potential memory-safety bugs in the decoder.
stephbook · · focus · HN ↗
wewewedxfgdf · · focus · HN ↗
It's a surprise that Google has let themselves lose the game given their infinite cash, massive computing resource, gargantuan information store/training data, and vast number of programmers.
The truckloads of ads revenue mean they don't have the single focus drive needed to win.
VirusNewbie · · focus · HN ↗
handfuloflight · · focus · HN ↗
osti · · focus · HN ↗
matthewfcarlson · · focus · HN ↗
jjice · · focus · HN ↗
LoganDark · · focus · HN ↗
bel8 · · focus · HN ↗
And I wonder if Google's main monorepo is already in Anthropic/OpenAI training data because of some stubborn dev.
krat0sprakhar · · focus · HN ↗
lunarboy · · focus · HN ↗
heyjamesknight · · focus · HN ↗
mattlondon · · focus · HN ↗
Behind how?
wewewedxfgdf · · focus · HN ↗
mattlondon · · focus · HN ↗
If you have actual independent benchmarks and evidence about how this new model release is "so far behind" and refutes the stuff from their blog then please do share because I think we'd all love to see that?
wewewedxfgdf · · focus · HN ↗
mattlondon · · focus · HN ↗
With respect, I don't find your arguement about them being "so far behind" especially convincing.
[deleted] · · focus · HN ↗
[deleted]
fwip · · focus · HN ↗
fjejfjdnjsjc · · focus · HN ↗
[dead]
dhdjcjcjnd · · focus · HN ↗
gniv · · focus · HN ↗
[deleted] · · focus · HN ↗
[deleted]
georgemcbay · · focus · HN ↗
I fundamentally don't understand LLM "brand loyalty".
All of the models are constantly leapfrogging each other and always have been.
Google had a long lag between releases (and still hasn't released Argon), but why wouldn't they be able to compete? It isn't like any of this stuff requires secret knowledge, the Bitter Lesson has proved true again and again, and Google can certainly scale computation, it is like the one single thing they've always done well in spite of all their other foibles.
singingtoday · · focus · HN ↗
786562354238 · · focus · HN ↗
wewewedxfgdf · · focus · HN ↗
ASalazarMX · · focus · HN ↗
- Person 1: X is garbage compared to Y!
- Person 2: Why?
- Person 1: Because I like Y.
TacticalCoder · · focus · HN ↗
So Google is migrating codebases from C to Rust? That is interesting...
jasonjmcghee · · focus · HN ↗
what about input?
(Maybe I missed it)
murkt · · focus · HN ↗
jasonjmcghee · · focus · HN ↗
And was 2M tokens IIRC after release.
There were also many rumors that Gemini 4 was going back to 2M. Just seems odd not to say what it is.
MisterBiggs · · focus · HN ↗
VirusNewbie · · focus · HN ↗
nananana9 · · focus · HN ↗
nikope · · focus · HN ↗
lanthissa · · focus · HN ↗
I think that should be a really bad sign, but hope its great.
tamimio · · focus · HN ↗
LoganDark · · focus · HN ↗
alehlopeh · · focus · HN ↗
w4yai · · focus · HN ↗
LoganDark · · focus · HN ↗
lukax · · focus · HN ↗
scirob · · focus · HN ↗
taylorfinley · · focus · HN ↗
Edit to add the fix: <a href="https://gist.github.com/birep/6f2c8d490c7a29820997d57bd654c351" rel="nofollow">https://gist.github.com/birep/6f2c8d490c7a29820997d57bd654c3...
spankalee · · focus · HN ↗
I use a mix of Fable 5.1, Opus 5.5, and Gemini 3.8 Flash and Gemini holds it's own. Especially in writing, frontend, and sysadmin work. agy for configuring a NixOS system has been truly incredible.
mapontosevenths · · focus · HN ↗
I cancelled Ultra because they forced me into their harness like I should adapt to them, rather than the other way around.
drusepth · · focus · HN ↗
I actually just cancelled Ultra also because I couldn't subscribe to a YouTube Family plan while I had it active (Google... :[) but trying to use Codex as a replacement while I testdrive Astra makes me yearn for agy again.
esafak · · focus · HN ↗
walthamstow · · focus · HN ↗
KeplerBoy · · focus · HN ↗
macNchz · · focus · HN ↗
That said, compaction feels like an idea that should work reasonably well, but across all of the major providers and agent tools I've used has never actually produced compelling results, to where if I see I'm getting close to the token limit I prefer to start putting a bow on the project and readying it for a fresh start. Even when I provide a detailed compaction prompt it usually focuses on the wrong stuff.
Vacyyyy · · focus · HN ↗
macNchz · · focus · HN ↗
marcus_holmes · · focus · HN ↗
Still works better than compaction.
rnxrx · · focus · HN ↗
On another environment I've been doing something roughly similar, but have integrated Hindsight as a kind of all-in-one of the above and am still trying to suss out the best compaction strategy.
mikepurvis · · focus · HN ↗
Mentioned by the author in a recent HN thread, I'm also experimenting with automating this through a tiny issue tracker called epiq [1] that basically lets the agent sessions themselves file tickets with the follow-on tasks and relevant handoff right in them, and then a dispatcher automatically launches those tickets into new agent sessions.
[1]: <a href="https://ljtn.github.io/epiq/" rel="nofollow">https://ljtn.github.io/epiq/
varman11 · · focus · HN ↗
mikepurvis · · focus · HN ↗
I assume Anthropic & friends have noticed this as well and will change how they handle long running sessions, so the gap will likely close over time, but this is definitely where things stand today.
[deleted] · · focus · HN ↗
[deleted]
w0m · · focus · HN ↗
Same teamates also post 'Sol deleted my git repo!' or 'Sorry, ignore those 300 PR comments i was just looking!' ~once a month.
sroussey · · focus · HN ↗
honr · · focus · HN ↗
tobias2014 · · focus · HN ↗
parasti · · focus · HN ↗
adastra22 · · focus · HN ↗
sigseg1v · · focus · HN ↗
What are people using 1M context window for?
piyh · · focus · HN ↗
I have a skill that spins up worktrees and isolated services on unique ports so I can work in parallel. Antigravity queues all my prompts and makes me confirm to submit them anytime a long running process like a hot reloading UI is active.
The models are fine, the limits are generous, but the dev experience shit tier. Before they were a Codex clone, AntiGravity was an IDE and during the transition to a clone they outright deleted my IDE. It took them a week to roll out a fix.
For almost a year they didn't allow you to see usage limits. Then when they did show them, they update every ~30 minutes and require 4 clicks to navigate to. It's a little better now, but it's still painfully behind the curve.
throwuxiytayq · · focus · HN ↗
miroljub · · focus · HN ↗
Do you know a single product from Infosys / Cognizant / Tata done right?
gitowiec · · focus · HN ↗
miroljub · · focus · HN ↗
speerer · · focus · HN ↗
p_l · · focus · HN ↗
kaszanka · · focus · HN ↗
arizen · · focus · HN ↗
sorrybutidontha · · focus · HN ↗
sarjann · · focus · HN ↗
KeplerBoy · · focus · HN ↗
levelZero · · focus · HN ↗
SomaticPirate · · focus · HN ↗
smartbit · · focus · HN ↗
gemini-cli supported 'pre-write diff tabs' (y/n) in external editors like vscode. In Claude Code I heavily use 'pre-write diff tabs' for documentation and miss it sincerely in agy cli.
IMHO Gemini 3.8 flash is fast and good enough, but the agy-suite is below par to say it nice. Someone else in this thread calls agy a terrible harness which is probably more accurate.
Kostchei · · focus · HN ↗
smartbit · · focus · HN ↗
I'm referencing this but can't see change in daily work: v2.14.0 (September 15, 2026) "New Permissions System" [1]
Details: Introduced the new unified permissions system, presets (Default, Request Review, Turbo), syntax-highlighted permission requests, and restructured the settings under Global Permissions and project-level Inherit Global.
[0] <a href="https://antigravity.google/docs/cli/modes/#available-modes" rel="nofollow">https://antigravity.google/docs/cli/modes/#available-modes [1] <a href="https://antigravity.google/docs/changelog/" rel="nofollow">https://antigravity.google/docs/changelog/
Phineas_here · · focus · HN ↗
LoganDark · · focus · HN ↗
augusto-moura · · focus · HN ↗
Phineas_here · · focus · HN ↗
KshitizLoharuka · · focus · HN ↗
[dead]
KshitizLoharuka · · focus · HN ↗
[dead]
tiborsaas · · focus · HN ↗
dleslie · · focus · HN ↗
They've got Zed, VSCode, Jetbrains... But no Emacs or NeoVIM
p_l · · focus · HN ↗
dleslie · · focus · HN ↗
I would rather not risk my Google account.
p_l · · focus · HN ↗
It does mean however that it cannot operate as flexibly as it it could with raw API, IMO, but agent-shell is essentially designed towards wrapping the official clients
dleslie · · focus · HN ↗
While it may be technically allowed, I'm not about to risk my account. Google has proven themselves to be capricious and arbitrary when it comes to TOS enforcement, and their appeals system doesn't meaningfully exist in practice.
p_l · · focus · HN ↗
dleslie · · focus · HN ↗
<a href="https://antigravity.google/docs/ide/extensions/" rel="nofollow">https://antigravity.google/docs/ide/extensions/
What I see is integrations for specific editors.
p_l · · focus · HN ↗
[1] <a href="https://github.com/agentclientprotocol/registry/blob/main/antigravity-acp%2Fagent.json" rel="nofollow">https://github.com/agentclientprotocol/registry/blob/main/an...
[2] <a href="https://antigravity.google/docs/ide/extensions/zed" rel="nofollow">https://antigravity.google/docs/ide/extensions/zed
dleslie · · focus · HN ↗
But thank you, it appears there is an official and generic ACP client.
mapontosevenths · · focus · HN ↗
I also had that weird Youtube problem. I had to go without it for several days because signing up for Ultra hijacks your YouTube account for no reason.
1) Try to integrate agy into a workflow. It can't do standard I/O like: tail -200 app.log | claude -p "Find the problem"
2) Hard iteration limits. Preventing runaways is good. Preventing me from looping on purpose is anti-user. See also number 7.
3) Not open source so I can't fix any of these problems.
4) No skills. In 2026. Yikes.
5) No persistent memory (see Claudes auto memory)
6) No sub-agents or orchestration of any type really.
7) Weird hard coded limits and constant API errors on everything (scaling problems?)
8) No /loop command
9) /btw is weird and ephemeral. No way to merge it back to the conversation.
10) Unstable in general.
11) No way to control it via API.
I could keep going on. I would suggest taking a class on Claude Code or Codex then using it for a few months. Swapping is always painful, but it's so worth it. Then if you want try to go back to agy. Don't worry, agy won't have changed much. It improves at a snails pace.
trevorm4 · · focus · HN ↗
thanhhaimai · · focus · HN ↗
I'm not sure this list is correct. Number 4 is especially wrong, since Skills are available with the launch of Antigravity 2:
<a href="https://antigravity.google/blog/introducing-google-antigravity-2" rel="nofollow">https://antigravity.google/blog/introducing-google-antigravi...
anyg · · focus · HN ↗
p_l · · focus · HN ↗
drusepth · · focus · HN ↗
krisgenre · · focus · HN ↗
Luckily for me both expired yesterday and I was able to subscribe back again (first Youtube family and then Google AI plan).
edg5000 · · focus · HN ↗
krzyk · · focus · HN ↗
esafak · · focus · HN ↗
krzyk · · focus · HN ↗
I like CLI more than TUI, and TUI more than GUI where appropriate. For working with text TUI is better, for e.g. images GUI (GIMP).
crossroadsguy · · focus · HN ↗
nsonha · · focus · HN ↗
antonvs · · focus · HN ↗
All the AI-generated UIs I've seen have been very derivative, certainly not eliminating any of the disadvantages of typical GUI interfaces.
Realistically, the whole "overlapping windows" GUI model, and everything that derives from that, was a metaphor geared towards people who'd never seen a computer before. It fit the increasing consumer focus of computing interfaces. It's no wonder that technical people often prefer TUIs.
Maybe AI will bring real advancements in GUIs, but someone's still going to have to make it happen.
nsonha · · focus · HN ↗
That is what we need, and if you're making the argument that a terminal shell is the best place to provide them then I don't know what to say.
antonvs · · focus · HN ↗
It's not that GUIs are inherently worse in principle, but in practice they often are.
The point about overlapping windows is that that "desktop" model permeates the thinking about GUI design, but it's fundamentally limiting and misguided.
> we need complex (but not overlapping windows, sure!) interactivity and rich display capability.
Yep. Pity today's GUIs can't deliver that.
crossroadsguy · · focus · HN ↗
nsonha · · focus · HN ↗
agentcoops · · focus · HN ↗
Perlis has an aphorism for this, as he does every important problem [0].
[0] <a href="https://www.cs.yale.edu/homes/perlis-alan/quotes.html" rel="nofollow">https://www.cs.yale.edu/homes/perlis-alan/quotes.html
nxdmum · · focus · HN ↗
In today's world - and idea stated stated is an idea stolen .
cowl · · focus · HN ↗
dmos62 · · focus · HN ↗
imtringued · · focus · HN ↗
It's missing the point. I mean think about the basics, why open the huge bash hole only then to have to close it? If you think about it logically, the only way you can sandbox bash is by writing your own bash implementation specifically for agentic use cases.
adastra22 · · focus · HN ↗
dmos62 · · focus · HN ↗
adastra22 · · focus · HN ↗
dmos62 · · focus · HN ↗
adastra22 · · focus · HN ↗
What benchmarks are usually good at is showing to what degree new models are better than old models. What they are not good at, by construction, is showing that harnesses are well adapted to how people use them.
dmos62 · · focus · HN ↗
adastra22 · · focus · HN ↗
Why? Because 4.6 actually talked like a human being. It actually organized its thoughts well, and got the main information across without the wall of text that makes your eyes glaze over. So from the perspective of human-computer interaction and maximizing the productivity of a developer+agent team, 4.7 and 4.8 were regressions. Despite much better benchmark performance.
Even if we consider autonomous agents, that benchmark is not indicative of how well they will interpret *your* requests. Or how well they will interact with other agents in a flock/swarm situation. The benchmark just doesn't cover this. (And the difference can be nontrivial! Sakana AI's published results show two generations of uplifting potential from better harnesses.)
crossroadsguy · · focus · HN ↗
adastra22 · · focus · HN ↗
tikkosam · · focus · HN ↗
edg5000 · · focus · HN ↗
pjc50 · · focus · HN ↗
This sort of thing alarms me. Having a $bigcorp account becomes a ""social credit"" system where they can ban you from all your personal stuff if they decide that you (or your agents!) are doing stuff they don't like.
w0m · · focus · HN ↗
runamok · · focus · HN ↗
nout · · focus · HN ↗
eloisant · · focus · HN ↗
mapontosevenths · · focus · HN ↗
tcoff91 · · focus · HN ↗
I don't want to mess with antigravity because my google account is too entrenched in my life.
shmoogy · · focus · HN ↗
8note · · focus · HN ↗
without having an entirely separate google account with its own separated bans, theres just no ability to trust those
Sabinus · · focus · HN ↗
jsw97 · · focus · HN ↗
rdtsc · · focus · HN ↗
spankalee · · focus · HN ↗
mapontosevenths · · focus · HN ↗
gchamonlive · · focus · HN ↗
ForHackernews · · focus · HN ↗
gchamonlive · · focus · HN ↗
ajolly · · focus · HN ↗
gchamonlive · · focus · HN ↗
moecables · · focus · HN ↗
Conscat · · focus · HN ↗
starfallg · · focus · HN ↗
lp92 · · focus · HN ↗
mpweiher · · focus · HN ↗
Not only could it not complete the small task, the code was obviously wrong from looking at it and did not even compile.
When I pointed that out it got pissy and insisted the code was perfect and I didn't know how to use a compiler, or the compiler was buggy. Pasting the compiler errors did not help.
Surreal.
moffkalast · · focus · HN ↗
Is that a reference to <a href="https://xkcd.com/353/" rel="nofollow">https://xkcd.com/353/
gchamonlive · · focus · HN ↗
jmaker · · focus · HN ↗
pdntspa · · focus · HN ↗
noahmichael89 · · focus · HN ↗
IndeanCondor · · focus · HN ↗
seanthemon · · focus · HN ↗
mapontosevenths · · focus · HN ↗
ody4242 · · focus · HN ↗
barrenko · · focus · HN ↗
alightsoul · · focus · HN ↗
warkdarrior · · focus · HN ↗
aspect0545 · · focus · HN ↗
FranzFerdiNaN · · focus · HN ↗
Also I hope you don’t have children, eat meat, travel, have a car, run AC, buy things in other countries and such. Those things all take way way way more natural resources.
hexfish · · focus · HN ↗
qmr · · focus · HN ↗
scarmig · · focus · HN ↗
qmr · · focus · HN ↗
articulatepang · · focus · HN ↗
Patches to open source software are public goods. Your using them doesn’t prevent others from using them. So if you spend resources creating a public good, it’s in everyone’s interest to share it.
dzhiurgis · · focus · HN ↗
alightsoul · · focus · HN ↗
dzhiurgis · · focus · HN ↗
AuthAuth · · focus · HN ↗
luckydata · · focus · HN ↗
baby_souffle · · focus · HN ↗
Why would the guy who wrote curl share it? We can all build our own now...
Why do the Linux folks need to be so selfless? We can all build our own kernel now...
folkrav · · focus · HN ↗
otabdeveloper4 · · focus · HN ↗
dominotw · · focus · HN ↗
taylorfinley · · focus · HN ↗
imtringued · · focus · HN ↗
in amdkfd and hsakmt
Yes, that means AMD is sitting on both sides. They wrote software that doesn't work with their own software.
bel8 · · focus · HN ↗
Asked pi agent it to identify the main hero sprite size of game I was running. It had a ton of shader effects so it was hard to determine.
It used some cli tools to identify that it was a game made with Godot, decompiled the executable but data was encrypted, broke the encryption after writing a brute force tool to test keys extracted from the exe, then proceeded to extract the game gd scripts and assets, only to answer the question of the sprite size.
seanthemon · · focus · HN ↗
warkdarrior · · focus · HN ↗
bel8 · · focus · HN ↗
Still impressive that it did so much just to answer my simple question.
amanguliani · · focus · HN ↗
onlyrealcuzzo · · focus · HN ↗
I'm using it to run overnight tasks, and that's it until my quota runs out.
Canceled my subscription.
amanguliani · · focus · HN ↗
tourist2d · · focus · HN ↗
[dead]
8note · · focus · HN ↗
its a lot less chatty imo
awakeasleep · · focus · HN ↗
In the local app interface the winning choice is “efficient” and then turn off the sliders for warmth enthusiasm emoji etc.
It makes openai models so good to talk to i really have trouble switching.
unconscionable · · focus · HN ↗
Also canceled my ChatGPT Pro $200/mo subscription. Their Oct 30 price hikes and slow GPT-6.1 model has me looking for alternatives.
directdev · · focus · HN ↗
[dead]
gottorf · · focus · HN ↗
staticman2 · · focus · HN ↗
MILP · · focus · HN ↗
robobo96 · · focus · HN ↗
mattjoyce · · focus · HN ↗
nkozyra · · focus · HN ↗
xdavidliu · · focus · HN ↗
- AI is just a tool, like excel; it does what the human operating it tells it to
- next token prediction cannot be true understanding
- models can have no desires and goals, don't anthropomorphize it
However, "hallucination" is very much not one of them
gottorf · · focus · HN ↗
alluro2 · · focus · HN ↗
It didn't work. Gemini: "Oh yeah, that obviously cannot work, it's not possible to do it through OBD2" (paraphrasing)
It was quite funny to me, but a bit less so to my colleague.
Gareth321 · · focus · HN ↗
mattjoyce · · focus · HN ↗
rdtsc · · focus · HN ↗
mattjoyce · · focus · HN ↗
krapp · · focus · HN ↗
The bigger problem is that people expect LLMs to know what facts are. That assumption is even baked into the term "hallucination." Someone who hallucinates is expected to otherwise have a grounding in objective reality, to "not" hallucinate, and to be able to recognize reality from fantasy. We wouldn't allow a person who "hallucinates" as much as an LLM anywhere near the roles we give to LLMs. But everything an LLM does is as much a "hallucination" as anything else, it's just stochastically generating grammar. Some grammar just happens to be useful because of the quality of its training data, which was probably created by humans who do possess interiority and awareness of fact.
And it isn't "broken" either. Broken assumes that the correct mode of operation is to act as a source of truth or fact generation. When LLMs "apologize" for bad results, for instance they aren't actually apologizing. Try getting it to apologize for returning the correct data. It probably will. There is no cognition happening. It doesn't know either way. It isn't a calculator crunching numbers or a computer doing data analysis. It's just pattern matching.
"Hallucination" is no less correct than "confabulation" which also presupposes intent and contextual awareness. Unfortunately the way LLMs operate is so unintuitive (as opposed to the intuitive nature of the interface) that the only language we have to describe it is the language of human behavior, with all of the biases and false assumptions that brings.
UpsideDownRide · · focus · HN ↗
WarmWash · · focus · HN ↗
I'm assuming that Argon has at least a June 2026 date, but man, the 3 series models were a mess with newer information.
blinding-streak · · focus · HN ↗
> The knowledge cutoff date for Gemini 3.8 Flash is March 2026
<a href="https://deepmind.google/models/model-cards/gemini-3-8-flash/" rel="nofollow">https://deepmind.google/models/model-cards/gemini-3-8-flash/
WarmWash · · focus · HN ↗
The "some domains" are very narrow. They likely just RL'ed popular queries.
Gareth321 · · focus · HN ↗
Of course, it's called "flash," and that implies its purpose. I have little use for speed and a LOT of use for accuracy, so I'm hopeful 4.0 is much better. I saw a benchmark earlier today showing that it is much less prone to hallucinations. Let's see.
esafak · · focus · HN ↗
Gareth321 · · focus · HN ↗
yegle · · focus · HN ↗
And I saw it do this twice, once for Android 14 and once for Android 16.
I think this is just within 3.8 flash's capabilities.
p_l · · focus · HN ↗
Including going first for decompiling AGY binary instead of searching the web for documentation...
IshKebab · · focus · HN ↗
illwrks · · focus · HN ↗
martythemaniak · · focus · HN ↗
Grimburger · · focus · HN ↗
completely offtopic but is rolling with rocm worth it? I spend a fair bit monthly on rental gpus for projects and going to upgrade at home instead, AMD has some solid winners here pricewise but get conflicting reports about using it for ML in 2026.
once upon a time it seemed unthinkable to use anything but nvidia but seems to have come a long way since I last looked, probably would be just pytorch and gemma 31B
I get the feeling the situation is only going to improve longer term so might be a good time to just do it
esseph · · focus · HN ↗
clw8 · · focus · HN ↗
nzeid · · focus · HN ↗
ROCm promises a 30-50% prompt processing speedup. This is REALLY important for my workflow so I've been trying to get this shit to work for months. But no release before v10 worked well enough with any engine for it to matter.
The llama.cpp release binaries for ROCm (10) FINALLY work on gfx1501 and its relatives (with the correct shell variables), but the prompt processing boost doesn't materialize and the token generation speed decreases.
There continues to be a chronic problem across all engines with the ROCm integration for UMA devices. The good news is that some improvements have been made to that end for Vulkan, so more recent llama.cpp Vulkan binaries are now faster.
gcy · · focus · HN ↗
cyanydeez · · focus · HN ↗
solaire_oa · · focus · HN ↗
I say this is awesome, even as I glossed over the README and vomited in my mouth. The halogen repo looks like the same utter AI bullshit littering GitHub. But this one delivers, in spite of it's slop-riddled hallmarks.
In any case, yeah, ~55 tok/s on a high quality model, the mind reels at what I might be able to do without constantly beancounting token ratelimits. And it's a huge win for privacy as well.
cyanydeez · · focus · HN ↗
lardo · · focus · HN ↗
taylorfinley · · focus · HN ↗
danpalmer · · focus · HN ↗
dcl · · focus · HN ↗
danpalmer · · focus · HN ↗
I've tried Codex as a harness too, and that was nice. I don't find a significant difference between Antigravity and Codex. Codex has more features but I don't use them.
iknowstuff · · focus · HN ↗
la6479 · · focus · HN ↗
[dead]
plasticchris · · focus · HN ↗
_heimdall · · focus · HN ↗
I have a client app on a very old (for the JS world) version of eleventy using NetlifyCMS (also outdated). Claude has quite easily picked that up to add features to it along the way.
jubilanti · · focus · HN ↗
Being able to edit and recompile pretty much any part of the OS and userland (often not even needing to reboot!) is not something that can be said about Windows for sure, or even lots of things on Macs too.
x-complexity · · focus · HN ↗
Even if the source code's old, the fact that it is publicly available makes it much easier to train & improve on than if it were walled off.
augusto-moura · · focus · HN ↗
matsemann · · focus · HN ↗
Sammi · · focus · HN ↗
I used to be afraid of Arch, because I don't want a system that takes work because I'm already busy with work. But now I love it, because the LLM can tweak every knob and fix every issue for me, so it ends up being the OS that takes the least work to use. Get an error message? Tell the LLM and they fix it. Something not working exactly like you like it? Tell the LLM and they tweak it for you. This also works to great effect on Win and Mac, but not to the same extreme degree as it does on Linux and especially Arch.
lukan · · focus · HN ↗
Anything I want different now, I just tell the LLM to do it for me.
(For example I can now close lots of windows of the same type with 1 click, not 3, my whisker search now finds files and folders and I am able to run games that refused before)
I still ocasionally run into the usual linux driver issues, but not for much longer I suppose. I probably could fix some driver bugs now already if I point fable towards it and pay some attention.
In theory I could do all this before myself, but not just like that in some minutes, but in days/weeks/months ..
Sammi · · focus · HN ↗
masto · · focus · HN ↗
Drifted off my point a bit, which I guess was meant to be it’s not necessarily Linux-specific training.
c0n5pir4cy · · focus · HN ↗
chinathrow · · focus · HN ↗
oldandboring · · focus · HN ↗
safog · · focus · HN ↗
Drivers, Coding environment setup etc. are great too and it's nice to have everything logged so the next (more powerful) agent can come and improve the thing once in a while.
UpsideDownRide · · focus · HN ↗
stefan_ · · focus · HN ↗
Since LLMs have been so successful at finding exploits it's been clearer than ever that the people so obsessed with enshittifying every system with ineffective (other than pissing you off and wasting your time) "secure boot" functionality were really just too ignorant to succeed at actual novel security work, so they focused on this make believe crap. Well, glad that's over.
samspot · · focus · HN ↗
I am still very happy with my switch to Linux. But if I didn't have the AI help I would say linux is still unacceptable platform for those not willing, able, and excited to get their hands very dirty.
tarokun-io · · focus · HN ↗
mirmor23 · · focus · HN ↗
Most llm could do it. Claude went from firmware thread -> rtos scheduler -> mcu reference manual -> hardware controller register interface -> vendor sdk -> problem identification and the solution to it in a matter of 30 minutes. Linux could be even easier since it is so well trained on.
d3Xt3r · · focus · HN ↗
[1] <a href="https://github.com/warpfront/hipfire" rel="nofollow">https://github.com/warpfront/hipfire
[2] <a href="https://github.com/julianmb/halofpx" rel="nofollow">https://github.com/julianmb/halofpx
qrify_app · · focus · HN ↗
[dead]
vinzenzu · · focus · HN ↗
crossroadsguy · · focus · HN ↗
p_l · · focus · HN ↗
KMnO4 · · focus · HN ↗
w0m · · focus · HN ↗
phmx · · focus · HN ↗
hope it's not run by multiple threads and dlsym is not allocating.
dom96 · · focus · HN ↗
None of the other AI labs do this. Really frustrating.
gengelbro · · focus · HN ↗
aqsnow · · focus · HN ↗
netdur · · focus · HN ↗
tom1337 · · focus · HN ↗
> Today, we’re announcing our new frontier model, Gemini 4 Argon, which is rolling out to a set of trusted cyber defenders through our Fairwind Program.
gravisultra · · focus · HN ↗
This is why I will never take any of these leading model houses seriously when they talk about alignment. They are literally complicit in genocide and the worst crimes against humanity imaginable.
bananaflag · · focus · HN ↗
osiris970 · · focus · HN ↗
retropragma · · focus · HN ↗
xnx · · focus · HN ↗
helsinkiandrew · · focus · HN ↗
<a href="https://www.bloomberg.com/news/articles/2026-09-30/google-grapples-with-employee-skepticism-about-new-gemini-model" rel="nofollow">https://www.bloomberg.com/news/articles/2026-09-30/google-gr...
bitexploder · · focus · HN ↗