I hate to pile on since it's already getting some criticism, but I agree. It's kind of a good example why designers don't purely rely on mathematically consistent designs. Getting things to "look right" often means shifting pixels here and there ever so slightly, so that the math is a bit off but it feels better on the eyes.
Generally agree with the idea of calm technology, but I feel like inlay hints are a bad example. They actively give me anxiety because it makes the code feel harder to read, it takes my attention away from the code, and it feels more awkward to edit the text because you have these virtual characters getting in the way and having to re-render as you type, causing a shift in your cursor position. It's not at all calming for me, lol.
Congrats on launching. I spent a decade trying to build a design tool. I think I built almost 40 prototypes, to various degrees of completion. Never got to a point where I felt it was good enough to share. It's an incredibly difficult thing to do, so kudos to you for sticking with it.
Thank you, and I know exactly what you mean. I myself have rewritten the entire engine ar least three times until I was happy with the performance and the overall outcome. It’s been a long learning experience. As a developer at heart, this project scratched every itch I had from a software engineering perspective :)
Yes. This. I read a post-mortem about developing v2 of an app last month because getting insight into the thought process of the builder is super interesting (to me). It's probably not for most people, but it definitely has an audience.
there are various little things scattered around the github org - a js framework, a treesitter grammar, some old docs, a vscode extension, a vim-style editor, an AI-powered code editor geared towards design, etc.
Are you still working on this? Because I like the words I see on your GitHub -- vim-style bindings, keyboard driven, sounds like you write a definition language for your designs, basically?
Lik Matry is to Figma as openscad is to traditional CAD (Fusion 360, etc)?
Though that does sound like a huge project to take on!
I don’t know enough about CAD products to evaluate that comparison, but the core idea was to expose language as a design tool. First through code, then through keyboard commands (hence the vim idea). It’s still pretty fun, but LLMs have changed the conversation around what a designer even is, and I’m currently re-evaluating.
Matry might pop up in another form. I’m considering turning it into an actual browser for designers. Right now designers are getting into the code and using Claude/Cursor to make changes directly. But they still have to know how to get the app running locally, which is a hurdle. So if they could just navigate to the site, make some design changes directly in the browser, Matry could then take the changes and create a PR on GitHub for them. Designer wouldn’t have to fuss with any dev tools. Kind of a cool idea.
I really think I might be done with Apple. The only thing keeping me using them is how much I hate Android. The _millisecond_ a competitor arrives, I'm dropping my iPhone like a bad habit.
Off topic, but is there anything specific that you hate about Android? I find it acceptable. I'm trying to cut down my phone usage so maybe I'm more tolerant.
I'm wondering what adjectives you hope to apply to a phone operating system. I'm content with mine when I don't have to think about it, for which "acceptable" seems about right, and discontent when I do.
GrapheneOS on a Pixel is that competitor. Open source, more secure than Apple, compatible with nearly all Android apps. It's all the positive aspects of Android without the downsides (Google).
I keep hoping and wishing for a daily drivable linux phone that's compatible with all the us networks to come along. I'll keep hoping and wishing. Someday I hope we will get there!
I tried something similar a couple years back, and fully agree. Safari is atrocious for trying to create a good mobile experience. It almost feels intentional.
It's important to understand that he's talking about a specific set of models that were release around november/december, and that we've hit a kind of inflection point in model capabilities. Specifically Anthropic's Opus 4.5 model.
I never paid any attention to different models, because they all felt roughly equal to me. But Opus 4.5 is really and truly different. It's not a qualitative difference, it's more like it just finally hit that quantitative edge that allows me to lean much more heavily on it for routine work.
I highly suggest trying it out, alongside a well-built coding agent like the one offered by Claude Code, Cursor, or OpenCode. I'm using it on a fairly complex monorepo and my impressions are much the same as Karpathy's.
I had the same reaction. So when people were talking about this model back in December, I brushed it off. It wasn't until a couple weeks ago that I decided to try it out, and I immediately saw the difference.
My opinion isn't based on what other people are saying, it's my own experience as a fairly AI-skeptical person. Again, I highly suggest you give it an honest try and decide for yourself.
Every time I get to sing Treesitters praise, I take the opportunity to. I love it so much. I've tried a bunch of parser generators, and the TS approach is so simple and so good that I'll probably never use anything else. The iteration speed lets me get into a zen-like state where I just think about syntax design, and I don't sweat the technical bits.
Whenever I need to write a parser, and I don't need the absolute best performance, I reach for the lua LPeg library. Sometimes I even embed the lua engine just so I can use that and then implement the rest in the original language.
There's a bunch of really interesting declassified documents if you want to go down a historical rabbit hole. A long time ago I remember reading top secret messages that were sent back and forth between Kennedy and his military strategists in the days leading up to the Bay of Pigs. Feels like reading history from the source.
Yeah I think it all boils down to culture. Tools like RFC (and anything else) can help propel a good culture forward. But you can't fix a broken culture with a tool.
reply