I said it's kinda cool. Like what more do you want? I could point out how useless it is in general, I can't say it would make a good learning tool, because it doesn't. But it is a novelty site that does make sound and show correct chord positions. Can you use it to compose something? Sure but the sound cutoff between chords and the need to pick a chord that strums down first before you can strum up means you'll always produce a sound you don't want and you can't even replicate picking.
I think you underestimate how creative people can be.
As a guitar substitute, sure, it's an approximation that can't possibly measure up. But as a modernized version of an autoharp, this could be a legit musical instrument.
The fact that it presents itself as a virtual guitar makes it accessible. You see it as a limitation. But limitations are actually great for creativity.
You are failing to answer the question. What's your point? I pose a question, I present what can be said, which sure I did say it in that comment to point at the extremes, but the question remains unanswered. What do you want of me? and now we have what's your point?
My point is hiding behind passive language like that is cowardly. You actively chose to do literally all of those things. It's not that you "could" do them, you did do them. Own up to it.
Ed Zitron is the most objectively and confidently wrong human re: anything going on in AI, competing only with the likes of Gary Marcus and, on his bad days, Yann LeCun.
Feb 2024: "I believe we're reaching the upper limits about what generative AI can do and how accurate its outputs can be."
July 2024: "Generative AI, as I said back in March, is peaking, if it hasn't already peaked. It cannot do much more than it is currently doing, other than doing more of it faster with some new inputs"
July 2024: "Generative AI models aren’t getting more energy-efficient, nor are they getting more “powerful”
August 2024: "generative AI is a dead-end technology that has peaked”
Dec 2024: "I also warned you in March that generative AI had already peaked.”
Jan 2025: "I believe we’re at peak AI"
February 2025: "Sam Altman deputizing Orion from GPT-5 to GPT-4.5 suggests that OpenAI has hit a wall with making its next model, requiring him to lower expectations"
April 2025: "It also, at this point, is pretty obvious that generative AI isn't going to do much more than it does today."
August 2025: "These models have clearly hit a wall where training is hitting diminishing returns"
Nov 2025: "the fact we're running out of high quality training data and we're hitting the walls of scaling laws, in the training paradigm, these models aren't getting better. What we're seeing today is pretty much what they're always gonna be like"
"Based on estimates of their burn rate and historic analyses, I hypothesize that OpenAI will collapse in the next 12-24 months unless it raises more funding than in the history of the valley and creates an entirely new form of AI." - Ed Zitron (Jul 29, 2024)
Yes, but clearly that's not what Zitron was implying. The rest of his thread's commentary makes that clearer. He's saying:
OpenAI is going to implode soon. They would have to raise an unfathomable amount of money, it's literally never been done and is so much it won't happen. That's why they're going to collapse.
He could have predicted that OpenAI would raise an unprecedented amount of money and are not going to collapse. He clearly believed differently.
People keep asking for this w/ Codex, too, and I really regret that both labs seem inclined to listen.
If you ask a thinking/research type question in 'Chat' versus 'Work' mode in these products -- say, something complex about politics, or do a multiturn business strategy, or want to work thru a new concept, you get very different answers.
The harness, steering, etc. in the chat/reasoning products is so much better for this type of question (that doesn't require code as a primary substrate).
Even as someone who mainlines like, 7 coding agents at all times, I regret that productivity fever will mean the regression of think-first-act-later AI UX.
I hope not Chat is still all you can eat and Work uses Codex tokens. I can see why they would want people to think they wanted this without thinking about how it currently works. If Chat starts eating tokens then there is not much reason to use Chat other than most people don't live in the command line like developers. Claude Chat / Cowork already eats tokens either way so not much of a change really. I have never used Work since if I want access to local files the CLI is a much better interface combined with an IDE, but can see the appeal to non-developers.
This is my main reason for not using Work. I was tempted to use a few "scheduled tasks" in ChatGPT, but once I found out they used Codex tokens I stopped creating new ones.
I built a terminal control plane and added an MCP server that runs on my Mac. It lets MCP clients create terminal sessions, send messages, read the contents, etc on my Mac.
The terminal sessions are running Luna on XHigh (on Pi) and GPT 6 Pro on ChatGPT.com is the main orchestrator.
Since ChatGPT and Codex have different limits, I can have 6 Pro orchestrate the Luna sessions. Using voice mode to talk back and forth about the software factory is really nice. Will be open-sourcing soon.
I recommend using Work sparingly because sometimes it is the better choice, but I do ration it. With Claude I simply don't use the web/app chat at all (and I have no idea what Cowork even does ngl, never used it) I think there's a Claude Design? No idea why I would need it (mostly, why I would spend tokens on it lol)
Claude Design is good at making a bunch of UI pages in a single design look consistent, and it's better at making an initial starting UI than just asking Claude Code. Think of it like Anthropic's version of Figma. It honestly works pretty good and I use it often and feel that it saved me a lot of time. It's pretty token heavy though.
GPT Chat seems smarter for business questions or planning that does not require iteration or wrangling data sources.
But Work gives the model a computer instance it can use for programmatic data access, API munging, etc.
Success cases I’ve had:
chat - read the reports in my Gmail and put a counter proposal together.
Work - cross reference all the options with commute time using traffic aware map data. Ground it on drop off / pick up times from each option’s stated rules and hours. Create a table with commute and idle time break downs.
The fact that it doesn't work well today doesn't invalidate the user need. Not everyone wants a terminal style interface. Traditional UX makes more sense especially if say you are accessing existing plugins and say kicking off a scheduling task - no way would I want to do that via a chat interface if I have the option.
I see Work as the mode where you can generate and edit files without manual intervention.
I tell chat to recommend me some books based on some of my favourites. Chat does it. I read some of them, liked some, disliked few. I give chat that information, it recommends me based on those, now I don't know which of the entries are relevant or not.
I don't want lock-in, so I try my best to tell it to generate copy-able MD syntax that I have to manually paste to an editor.
With Work mode, I tell the model to just maintain an append only markdown file, where it writes "still recommended", "not recommended any more", etc. beside titles. It does this after each turn.
This is just an example. Work - I see it as a mode that can maintain, update, and edit a file.
I agree that they should be separate modes, but presenting it as a toggle in the app is a terrible user experience.
The model itself should figure out how much “power” it needs to run the query. I’m just asking a question. Whether you need to do a simple internet search or spin up a VM and run scripts is up to you.
> The harness, steering, etc. in the chat/reasoning products is so much better for this type of question (that doesn't require code as a primary substrate).
I had this same thought recently. Is it possible to 'recreate' ChatGPT/Claude Chat easily in Codex or Claude Code? I assume it would roughly be just swapping the system prompt. Anthropic seems to publish theirs but I don't think OpenAI does
LLMs are inherently deterministic. The way everyone deploys LLMs leads to non-deterministic results, but there's nothing† stopping providers from offering deterministic evaluation if they choose.
All the sources of randomness are under the control of the provider, even if today's deployment structures mean providers introduce extra randomness due to the concurrent nature of the evaluation. Serialise the computation, feed it from a pRNG, and you have a fully deterministic result. But providers don't want to offer a deterministic result, and especially not one as fragile, expensive, and inefficient as a full serialisation would be.
†: For variants of "nothing" that include cost and deployment challenges.
This is technically true, but when people talk about randomness, its not only about same input-> different output, like temperature>0 and the things you said.
Its also about very similar inputs -> different outputs. Even with everything you said, yes, same input would result consistently into same output, but sliightly different input and you might get completely different/semantic answer.
There's deterministic enough, and then there's computer science non-deterministic. If I ask for a Todo app, I'm going to get a Todo app, even if the buttons get moved around and the background color of it is brown instead of purple if I ask today vs 6 months ago. If the AI completes the phrase "the capital of France is..." with anything other than Paris, something has gone more wrong than usual.
In one of the earlier iterations of this they at least made the UX distinguish Codex vs. ChatGPT which I really enjoyed.
I must admit I spent a little time in ChatGPT this weekend, thinking I was in Codex. After some unexpected behavior (disappointed) I realized my mistake.
The fact that people asked for it means that there is a demand for it. Maybe you aren't the target audience? One size can't fit all. People just have to adjust and go.
Yes the point is that they wouldn't have to adjust unless they are merged into one. Precisely because one size can't fit all, yet they insit on one size now.
I have a repo/project called Loadouts & Summons. It has a primary skill, `capsule`.
All skills, MCPs, CLIs, etc. live inside of it. I have it symlinked to all my dev machines so that it doesn't have to be an MCP.
`capsule` is then progressive to dozens of skills/tools thru `capsule` -- ex. `$capsule plannotator [args]`.
In some harnesses, I make it human-invoke only, and call it directly. In others, I let the model invoke it, and it has a top-level description that hints at what's inside.
Maximal context/session start control and capability extension.
