What I find fascinating that there is so little substance in this article about the quality of produced code and the medium. Is the code documented and tested? Is it understandable and extendable? Is it secure? What language, framework, database was used? Author mentions judgement and taste - well, is the code tasteful? Will the model rearchitecture the entire thing if I ask it to add new functionality, spending anot…
Less fascinating when you consider that this is a non-coders perspective.
So, the perspective of the one that gains the most, that will value this the most, and that will pay the most? ;)
This is completely fine, as those are your own installs, but LLMs can't be owned by the users, your Opus is the same Opus as everyone else's, your only difference is the suscription tier to their API. If you had your own on-premises LLM, that would indeed be your LLM, and it would make sense to compare it to the on-premises LLMs of other people, as your setup particulars would affect the result.
The copyright to the Outlook binary isn't owned by the users either, even if they're running it on local hardware. The Opus 4.8 weights are (we assume) the same between users, but the conversation/tooling state is not shared between them by default. I prefer to route around this construction myself, since I do think there's some ontological slippery-slope potential, but from a lexical perspective I think “my” is a pe…
> The copyright to the Outlook binary isn't owned by the users either, even if they're running it on local hardware
There was a time where one actually bought software to own it.
This time is.. actually it is right now. Please leave at once.
This 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.
Reminds me of a fun story. Some 20 years ago when I moved from Fort Frances to Toronto for college, my high school best friend was also going to college in Toronto, and his dad offered to drive us together in his truck with all our stuff in the back. We were saying our goodbyes and my buddies dad said to my dad "We'll get there a lot faster, I found a shortcut!" My dad, confused says "shortcut? there is no shortcut, just highway 1..." and his dad insists he found an alternative route, much shorter by kms and we'll fly up there 6 hours faster! Get into the truck and he pulls out 5 pages of printed mapquest... I assure you, having done it, Sault Ste. Marie to Sudbury via Elliot Lake on logging roads, may look interesting, but not correct, added a good 8 hours to the trip.
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.
> tells you surprisingly much about how the brain of person uttering it works
That's ridiculous. You wouldn't respond to "I went to visit my doctor yesterday" with "but slavery has been illegal since forever!" Similarly it would be foolish to respond to "where should we meet? my place or yours" with "but we both rent!"
What I find fascinating that there is so little substance in this article about the quality of produced code and the medium. Is the code documented and tested? Is it understandable and extendable? Is it secure? What language, framework, database was used? Author mentions judgement and taste - well, is the code tasteful? Will the model rearchitecture the entire thing if I ask it to add new functionality, spending anot…
>What I find fascinating that there is so little substance in this article about the quality of produced code and the medium.
I clicked one of his examples intrigued "a snake game where the snake is self-aware and crazy things happen;". Played for 1-2 minutes, and it's the classic 1980s snake game. Am I missing something? What is "self-aware" about it? Some funny messages at the bottom of the screen? And what are the "crazy things"?
I'm happy to discuss arguments if you want to add any?
Not OP, but for me, this model will get VERY expensive in 2 weeks. Now it is part of Pro plan, after 22nd it will get excluded and I will pay by token API usage (~10x more expensive).
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?
We see the same thing when new laptops are announced and every employee all of a sudden needs to upgrade, despite the fact that 90% of people would be able to make do with a Macbook Neo.
> despite the fact that 90% of people would be able to make do with a Macbook Neo.
Myth. Total myth! I recently had to beg for more RAM after continually hitting swap space which causes tools like dictation to stop working, failure to load certain websites without rebooting, and so on. Devs do in fact need powerful machines and the ~$500-1000 an employer saves upfront in machine costs is dwarfed by productivity losses.
Giving your engineering employees new machines in a 2-year cycle that are between the middle and high end is one of the cheapest ROI decisions that a tech org can make.