Okay, I just realized I'm lying. I went to use free gemini and asked "Can you do embedded HTML in the chat window like claude can?", it said it could so I asked it do "Pick whatever is easiest for you but most visually impressive or impressive complexity wise" for an example. It spit out this pretty damn impressive artifact in very little time. Gave it a couple tables in the style Claude makes for me and asked if it could do similar, in pics 2 and 3, and it spit out what's in pic 4. I'm pretty damn impressed to be honest. You might be right, if Gemini has frontier intelligence and good human like interaction/communicaiton skills like Opus 4.6 or GPT 4o this might be the ideal model/harness combo I've been looking for. Also the Google Black Friday prices right now are crazy good. 149/yr gives access to neon plus a bunch of other Google goodies. Some of which I'm already paying for, so almost becomes free for me to go back to Gemini.
You forget not everyone uses CLI. They still have the best normie harness between web and app of anyone. Not sure why OAi or Google still havnt done HTML embedded into the chat itself yet. You prompt GPT and still get ASCII diagrams and basic tables unless you push the model to do something a little nicer. Claude you get beautiful diagrams and colored text comparison tables etc. For none code users like myself it’s night and day. That all said I’ve hated most of their models after 4.6 for interaction and communication purposes. Hearing great things about neon in that regard is tempting me to go back to Google .
Odd, I've never seen GPT give a nice diagram. However I do use this in my preferences now to force the issue more often with Claude. Feel free to edit however.
"For explanations of complex systems or multi-layered topics: break long explanations into clearly numbered or headed sections with bold key terms inline. Keep paragraphs to 3-5 sentences max. Use sub-bullets sparingly for categorized lists (e.g., types of fiber deployment). Interleave 2-4 inline visuals (diagrams, illustrative drawings, comparison tables) throughout the response rather than consolidating into one. Use illustrative diagrams for "how it works" concepts, structural diagrams for architecture, and HTML tables for specs, subsystem breakdowns, and trade-off comparisons. Maintain full analytical depth — don't simplify — but structure it for scannability.
"
@greydel6@Mr_Derivatives Think of how many people he made buy from the highs all the way down to here. Prob has ruined at least 10,000 marriages in his posting career.
@LiebermanAustin You don’t realize the level of schemes Jensen was pulling to pump the bubble. The board fucked up and the only way to put the toothpaste back in is rehire Jensen and hope everyone else continues to look the other way.