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.
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.
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
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.
1 - thanks to the poster that mentioned nausea, I've been looking for the word to describe LLM based writing for a while and it's perfect.
"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
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)
"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.
We also have a discord server, lmk if you're planning on using BUI!