What are people working on that they see such a substantial difference between Mythos and Opus? I'd say I'm working with advanced stuff and more than often Deepseek is even more than enough. Why is everybody a genius in here?
[deleted]
What it feels like to work with Mythos
41–50 of 337 posts
Re: What it feels like to work with Mythos
#42Anecdote: I fed Fable some models I’ve been hand verifying (basically, I sketch out a scenario for Opus to model, it builds it, I ask it to show me the math, I correct it, we iterate like this, then I double check its code to make sure the math matches the model logic). Fable found almost every error I found, and then had some interesting suggestions for additional variables. It also burned through my usage quota lik…
now for the best question: whats your ROI here?
It will be great when the price of compute/memory drops to normal level!
Re: What it feels like to work with Mythos
#43Mollick runs the Generative AI Lab at Wharton, with all the corporate sponsors. He is a professor but sadly also an AI shill. He should switch to advertising washing power.
Ethan is a booster but I wouldn't call him a shill. He cites data and mostly in a fair way, though you could argue the sources he chooses to focus on are biased.
Re: What it feels like to work with Mythos
#44This is what he built: https://isochronic-passage-chart.netlify.app/ Doesn’t work too well on mobile but looks interesting
It looks interesting but, like a lot of AI, looks correct but is not. Most of northwestern Canada says you can get there by road. If you look at Google Maps, there's no roads there for quite awhile. I see one highway between Inuvik and Tuktoyaktuk but that's about it.
Re: What it feels like to work with Mythos
#45> It worked for nine and a half hours. > Again, it wasn’t perfect. As an expert, I was able to spot some errors and omissions (some as a result of the design I had asked for) that I had the AI correct That's the bit that stuck out to me - that's longer than I would expect to work on a problem in a day or even expect to go back & fix the output of something that has a core reward loop of hours. My customers are curren…
In Claude's defense (and I cannot believe I'm defending it), I know no single dev who could create what it did (Concord), from a 19-page design document, in 9.5 working hours. We're gonna go back to the days where our bosses ask why we're just sitting around, but instead of saying "compiling," we'll just say, "waiting for Claude."
Sadly I didn't get very many answers to my Ask HN, "What are you doing during inference?": https://news.ycombinator.com/item?id=47944917
Re: What it feels like to work with Mythos
#46What are people working on that they see such a substantial difference between Mythos and Opus? I'd say I'm working with advanced stuff and more than often Deepseek is even more than enough. Why is everybody a genius in here?
I’ve been working on implementing some common web infra type projects in Rust lately. Basically trying to use a lot of the great primatives in Rust like rustls (modern openSSL) and Tokio (async) to build memory safe or close, nginx drop in replacements.
A small portion of this effort is having a high quality Lua in Rust repo. I’m using mythos to fix some of the performance issues with my Lua interpreter that gpt 5.5/ opus 4.8 had stone walled on.
Not sure if Mythos will be able to crack this but it has been running for a couple hours now with some promising results.
Performance charts linked here if your curious https://github.com/ianm199/lua-rs
Re: What it feels like to work with Mythos
#47> First, how good is Fable? In experiment after experiment I conducted, it outperformed basically every other public model I have used by a considerable margin.
What makes me excited is that GPT 5.6 (its actually GPT 6) is going to be crazy
Re: What it feels like to work with Mythos
#48Earlier quoted context omitted.
Isn't it common to refer to all software like that? "Let my look at my JIRA", "I can't find anything using my Outlook's search function", "My Powerpoint is acting up today", "My browser just crashed" are all sentences I might say during a normal work day
Depends on the demographic I think. And also tells you surprisingly much about how the brain of person uttering it works. There are people that almost feel physical pain if something is unnecessarily incorrect. + That if the mental model of something is accurate, it is actually _more_ work to say something that is incorrect than just saying the correct thing.
In my mental model, "my Outlook" is the outlook instance running on my computer, on my data. My outlook crashed today. Yours might not have crashed. Similarly, my Jira contains tickets about my work, your Jira does not contain those same tickets. That might be technically the same instance on the same SaaS server, but the server I'm routed to accessing my data with my credentials turns it into "my Jira". My Jira is slow. Maybe you are lucky and get routed to a faster server, or your company is self-hosting. Then your Jira might be reasonably fast
Re: What it feels like to work with Mythos
#49I have been using it for less than an hour so take this with a grain of salt of being excited for the new tech.
In a project like mine (https://github.com/tsz-org/tsz) I am constantly frustrated that models were not doing enough research and were not taking into account other situations. Again and again models would produce code that would fix one thing and break 2 other tests that were "unrelated".
With Fable it seems like tasks are taking much longer (I have not seen a pull request from Fable sessions yet) but reading the transcription of those sessions I can see how it is doing the right thing by not leaving any stone unturned.
As the article says, it's hard to communicate this "feeling" about models because it is very project specific but I thought I share
Re: What it feels like to work with Mythos
#50Was the condition of being granted early access to this castrated model writing a post praising it?