Blender's UI and Runtime: Much Faster Than GPUI
github.com707 points by ppmpreetham a day ago
707 points by ppmpreetham a day ago
Can I please congratulate you on your README. It rapidly tells me what I'm looking at, and why I might be interested in the project. There are so many READMEs around that ... just don't do that. They ramble about technical implementation details, how their language choice is amazing, and a third of the way through the README, I'm still left wondering, "but what does this project do?".
I find it to be confusing LLM spam. It spends a lot of time talking about Qt APIs, and dearimgui... most of which could go in a separate page.
But the worst part is all code snippets are followed by an image which is not related to the code snippet. It's not what you get by typing the code... it's something completely different.
Many of my old >1K star GitHub projects were not that great, but I always made sure to create the cleanest, simplest possible READMEs, inspired by things like the Python requests library's docs (https://github.com/psf/requests). I think it helped a lot in their success.
I remember someone once created a GitHub issue requesting I turn the README into some verbose technical thing with full API docs and a bunch of people replied saying they greatly preferred the "pitch + high-level examples" style.
...really? for my part, after a few paragraphs i felt in my bones that i was reading undisclosed llm output and noped out of evaluating the entire thing any further.
but also the fact that yours is the most upvoted comment tells me there are entire swathes of people for whom that style works, and i am interested to get in people's heads about that, because it might yield some insight re: for what kind of audience these labs are optimising the style of text these models generate. so, if someone is reading this comment, and you broadly agree with the comment i am replying to, please answer these questions:
1. is english your native language?
2. what about the prose do you find appealing?
3. do you not find the structure (colossal wall of text, infodumping about largely irrelevant details) annoying/noisy?
4. does the word-to-word style and clichéd phrasing not immediately set off your llm alarm bells?
i guess people can answer if they disagree too, if they really want to
I liked the README, or what I read of it.
1. English is my native language.
2. The organization was to the point (eg it described what this is and who would use it up front). I can't say I found the prose "appealing" -- about the best I can say is that it was so obviously LLM writing that it implicitly told me that this is most likely a large mostly unattended porting project, which helped me set my expectations accordingly. Note that this is also why I stopped after getting a good feel for what it all is; the project would be interesting if I had a need to make something with that exact style of UI, but otherwise there wasn't going to be some shiny new idea or brilliant perspective that I could apply more widely.
3. Partly. It was a wall, but not that impenetrable a wall. There's plenty worse, and it was broken up enough for me to get through. Things were signposted well enough for me to skip a lot of what wasn't relevant to me.
4. Oh, absolutely. See above.
I'm finally growing the ability to extract value even after detecting that text is in the en-SLOP locale. Originally I couldn't detect it, then I could and couldn't tolerate it, now I'm starting to be able to treat it like broken English or caveman speak. I have to work to extract value, albeit a different type of work than those two.
It's mostly about suppressing my reactivity to the choppy phrasing and braggadocio (which are both the results of reinforcement training to elicit exactly the sort of reaction that I'm suppressing).
I could tell within a few sentences that it was naked slop, and I was grateful to be able to nope out rapidly, without missing anything.
It still sounds like LLM which is nauseating to read. For instance: "Blender's interface is famous for how it feels. You press a number field and drag: the cursor vanishes, the value glides under your hand, and you never hit the edge of the screen. " that's ChatGPT writing.
It is ALL AI generated I can say that because I recently worked on a landing page and wrestled with Claude Opus the WHOLE way through. Claude has no idea how to write copy. Neither do any of the others, you have to edit with a fine-toothed comb.
To the project maintainer: don’t ask people to read a terrible AI generated sales pitch novella that quantifies your AI generated port against every UI framework out there.
Here’s the obvious giveaways:
“ 4. The many ways in” “ Python, four ways”
“ tkinter: all 7,846 public names of tkinter and ttk. Nine real programs behave identically on the standard library and on BUI.”
“ Rust: the web platform, natively”
Ugh it’s excruciating. You’re better off with a readme that shows a few screenshots and installation instructions.
It also says it's all LLM explicitly near the bottom in the FAQ
My mind checks out when I see LLM prose. Didn't get that far.
With that much spew, yeah - I didn't read it all. Got about a paragraph in (signs were pretty clear already) and then skimmed looking for confirmation.
i am way too lazy to write good documentation. BUt i also dont want to have anyone read claudette-prose so i noticed that
"down to earth" and "hobby-project" does a good job. its still not perfect but better than the vanilla output. eg. https://github.com/busssard/OpenRing
This is why I stopped using Claude. ChatGPT is better in that regards, but you still have to write a ton of rules for it to read half-decent and then edit it manually anyway.
None of them is better than the others on the frontier. But to be honest, the models are designed for acing STEM exams not doing copywriting.
This is further evidence of the need for small models doing specific things well.
Where I would say models fit in the process is establishing the general layout of documentation and iteratively refining things out. Interestingly, it’s the same for image generation too. But 9 out of 10 it creates incomplete work that needs refinement.
Go wide, then hone in, refine. There’s no such thing as getting AI to single shot creative tasks. Which is funny because everyone thought writers are on the chopping block initially, but that is unequivocally NOT the case.
Even technical tasks, agents doing it their own way yields garbage in some right. It’s just a question of how long it runs before it goes down a path of no return.
Human in the loop is the only way. And, to be honest, what’s the f*king rush anyway? We all need to slow down. Good ideas with unravel in time. :)
it's funny how these claudese constructions also come out of lil baby local qwens and stuff too. i guess they're just directly distilling a claude endpoint, or whatever.
like, if people are gonna be turning the crank to generate prose-like text from statistical models and calling it a day, aren't "subagents" a hip new thing nowadays? there do exist models that aren't overcooked to impressively bad long-tail in the pursuit of maximum coding benchmark scores. such other models generate prose-like text that is significantly less miserable to wade through.
if you're a vibecoder who's terminally committed to the bit, for god's sake, at least tell a local gemma to draft your readme or something. an occasional outright falsehood is less damaging to usability than the experience of reading feeling like trudging through a pool filled with treacle. (mind, both are a violation of trust, and a failure to deliver proof of work, and please stop, but at least if the falsehoods are comprehensible and identifiable there's light at the end of the tunnel)
Thanks for the word nausea - I've been trying to put my finger on that - I kept thinking of sickness but that's too much, LLM nausea is definitely a thing.
Edit: I found reading those examples in the most sanctimonious voice I could imagine seemed very plausible - maybe LLMs sound like they are up their own arse.
Not to mention that it includes screengrabs! Which a shocking amount of gui and web projects dont do
I can't figure out if you're being sarcastic
The very first line of their README:
"Blender's user interface, as a library you can use from Python, Rust, JavaScript (React, Svelte), C, C++ and Dear ImGui."
This tells me a huge amount of what I need to know, if I'm interested in this project or not.
Compare it to another very recent example posted on hn: https://github.com/rivet-dev/rivet - You need to get some way down the page until it discloses what you might be able to do with the project. https://github.com/rivet-dev/rivet#use-cases
But by that stage, even though it isn't very far down the page, I'm already checked out.
thank you, I thought you didn't like it lol. let me know if you use it.
We also have a discord server, lmk if you're planning on using BUI!
I don't get this comment, the readme felt like slop to me. What makes this any better.. I genuinely want to understand why someone thinks this is a good readme sure I may have seen worse but I have seen much better readmes.
The very first line of their README: "Blender's user interface, as a library you can use from Python, Rust, JavaScript (React, Svelte), C, C++ and Dear ImGui."
Then, the README very quickly continues with "What BUI is" and "Why BUI exists". These are all the exact things I want to know, ASAP, when I encounter a new project. The language reads perfectly fine to me.
Here is another example of a nice README: https://github.com/mpv-player/mpv
Do you know what I don't want to know first? What the startup time is, what language you wrote it in (because you think it makes your project cooler), some other random internal details about the performance of the thing, when I don't even yet know what the thing is.
> what language you wrote it in
You mean something like:
> turns it into a standalone UI library with a small C core
...?
Or this:
> At the heart of BUI is the kit: a small runtime written in C
......??
I personally have no issue of this, but the more I read your comments the more confused I got.
I'm confused. Are you being sarcastic? Isn't this readme in the most typical LLM-ism?
They are not being sarcastic. The first first sentence tells you what it is.
If that's an LLM-ism, then it's one that I hope spreads.
I added Lua binding support for anyone looking for it, just got merged upstream ..
I love the general idea behind Blender's UI.
And I do appreciate the effort that goes into it, especially in the latest versions as it got much better,
But I really really really REALLY don't want that UI in anything else other than Blender.
Please don't.
If you're working on a small game project without an existing framework/platform, you usually build a really bargain-basement game editor alongside it. That editor takes a long time, and it's often spent in arranging UI stuff.
If you're already using Blender to make assets, there's some benefit to stuffing Blender's UI into your game editor too.
In that case it would be competing with imgui, egui and similar libraries, but the submission is comparing it to GPUI.
Do imgui/egui have comparable numbers of interface objects and parameters to adjust their look and behavior? I certainly wouldn't suggest either as an alternative to QT-level interfaces—which seems to be what's offered here.
>If you're working on a small game project without an existing framework/platform, you usually build a really bargain-basement game editor alongside it. That editor takes a long time, and it's often spent in arranging UI stuff.
Not in an age of AI.
I mean if you want to code all this stuff by hand, I get it. But that's a choice. And since it's a choice that means shoehorning a Blender UI into a "bargain-basement game editor" (and having a "bargain basement game editor) isnt really needed. You absolutely don't need to spend a lot of time arranging UI stuff.
Game tooling is pretty trivial now and it's not user-facing. Again, I fully understand why someone would want to do this themselves still but let's not pretend thats not a choice at this point.
Depending on what you and the other poster mean by "arranging UI stuff", AI could either solve the problem for you or create larger problems, especially if you're not opinionated on either technical or UI matters.
Just curious: if this is really the case, why are you even spending time commenting on and thinking about one particular UI framework or not? As a dummy still writing code and making games by hand, I know why it interests me, but isn't this like an archaic topic for you? What is there to actually gain or learn from one library or another? Can't you just think about high level concepts and pure ideas now? Spend money to do the rest?
I think it’s just about as weird as questioning somebody’s motives on an Internet comment thread. I certainly share GP’s opinion about game tooling, but i’m here because i still care about making good software and that involves learning about and navigating technological developments as they happen. Is that sufficient reason for you?
Edit: the snark I’m responding to has been edited out
But in this case, isn't the precise conceit that dev tools themselves don't need to be "user facing"? Why do you need to follow UI development for dev tool type things if you don't actually ever need to use the tools anymore? Why would you even spend the money getting the AI to add the slider it's never going to use?
You are reading them wrong. I think they mean “customer facing” instead of user facing i.e. the player doesnt care if the level editor has some jank: they never see it.
For the types of tools that your coworkers are paid to use, vibing a first draft and developing from there is so much more time and money efficient than writing by hand that you would be dumb to spend your tooling budget differently.
Thats how i read it. Someone still needs to use tools, no one is saying that claude is going to one shot mass effect 4 yet.
After trying blender for about 20 years I still find the UI/UX awful. I think a lot of the new blender generation has baby duck syndrome.
Blender had a very different ui before and a big redesign, so most people have different opinions between the old and the new design. It sounds like you find all of them awful. I find that surprising and wonder what 3d program you find have good ui.
I have used every version of blender and it has always felt harder than it should.
I have used 3Ds max, maya, lightwave, cinema4D, milkshape, wings, Houdini, unreal engine 1 - 5, Hammer, Threejs editor and probably more. The Blender UI is worse than all of the above.
At the time of blender's old ui 3Ds max had menus nested 5-6 level deep in an ui that would make gimp very good design. Between that 3Ds max praise, conflating old blender ui and new blender ui, and not providing any specifics on what makes blender so bad (I just provided some about 3D max) I have to assume there is no truth to it. We will agree to disagree. I think blender ui is excellent, but a 3d editor is a specialised app.
I learned on blender and now all the other editors are ruined for me. I wonder why they haven't added a blender mode at this point for people who want more expressive use.
Zbrush is ok.
With 3Ds Max listed as good UI we really must just have different tastes, hah! :D
You've given quite a list of tools with different purpose.
For 3D work I would personally rate
Modo 3D, Zbrush > Blender, Houdini > Softimage XSI > Maya > space intentionally left empty :P > 3Ds max
Blender UI looks very nice and is very customizable. I think it's "ok" in beginner discoverability (none of 3D softs is great at that really) but when you get experienced with it it's one of the best.
I really like how they managed to keep all the tools and views pretty consistent given how many things you can do in it. Whether you are working on objects, vertices, nodes, movie clips you get the same shortcuts where possible.
> I think a lot of the new blender generation has baby duck syndrome.
Maybe some of them do, but even though I disliked the UI at first, I've come to appreciate it as I've learned it. It's simply different from most other software, so that obviously causes friction. However, I think once you learn it, it's quite a good system. There's a tradeoff between optimizing for familiarity/new users, and providing an optimized experience for advanced users.
I'm not a professional designer or 3D modeler but I've used Blender quite a bit. I know what you mean but the latest UI post redesign isn't bad.
Blender does a LOT of stuff. Its not an easy product to create an UI for. But I think the problem is much bigger when coming from a different 3D package than when learning from scratch.
My teenage kids use Blender as the first 3D package they've ever learned. I was impressed with how quickly they ramped up through videos and learning from each other.
I agree, I don't think blender has changed as much as people say. But I don't think it is baby duck, I think blender always had a good UI, it has just taken the rest of the world 20 years to catch up.
A lot of people go "Blender UI was horrible, but they redesigned the whole thing and now it is good" Having used blender in a minor role for 20 years(i think I started on 1.7), I think this was just a big psyop by the blender team. Sort of how the client goes "Change things" and you change nothing, wait a day, and tell the client "I made the changes you requested" client: "I love it"
I am not saying the blender team has not made substantial improvements to the UI over the years, but the core is still that same quick blender workflow, This is very different from the normal clunky GUI design of 3d modelers of the era and as such blender got a reputation for having a weird UI which was easily translated to blender having a bad UI. So what do you do when you have an unwarranted bad reputation? Especially now that the rest of the world has caught up and is using your flows and they are not so weird anymore. Make a dark mode and put out a big press release "we redesigned everything, it's good now" so people will try it.
I feel like the 2.49 to 2.6 update was a bit overblown, but the 2.8 update was pretty damn massive to me eyes
First time I hear "baby duck syndrome".
> Baby duck syndrome is a cognitive bias where people automatically prefer the first system, interface, or product they learn to use, judging all later versions or alternatives by how well they match that initial experience.
That's actually extremely common in scientific (GUI) software. And in any professional setting I guess.
> That's actually extremely common in scientific (GUI) software. And in any professional setting I guess.
I don't think that qualifies. There's an important distinction to be made between an aesthetic preference versus a professional not appreciating a tool being mucked with. Anything that interferes with my workflow without immediately providing substantial benefit is something that's actively harmful. In fact even if it does hypothetically provide huge benefits I still might not want to deal with it right this second.
......huh?
So if it's for an employer it's rational but if you're making the same choice for yourself it isn't? If one of those is baby duck syndrome they all are.
I think they're noting how the nature of baby duck syndrome might depend on whether the change introduced is within something that is for work or for play.
As in, that people who refuse change in their play activity are in some way different (less rational? more "syndromatic"?) than those who refuse change in their breadwinning activity.
I see the distinction, but am not sure I agree. It's just a neurotype spectrum of the same phenomenon. Baby duck is baby duck
Not quite. The distinction is between avoiding an articulable and concrete negative impact versus mere aesthetic considerations. For example, this pan is more difficult to use because it is somewhat undersized for what I'm trying to cook versus I don't like this pan because it's the wrong color or has the wrong accents or whatever. I understand baby duck syndrome to refer to the latter - ie having an unsubstantiated bias towards aspects of the thing first encountered.
I'd only point out that undersize and oversize aren't purely objective concerns, but are also aesthetics compared to what you're used to.
I wouldn't be arguing about this except that I can't trust my clock app on my phone because some bozo keeps redesigning it to work a different way every 6 months