Well done. Here’s hoping that a hand-written GPU backend gets developed based on this wonderful proof of concept. There’s no reason to not take advantage of the state of the art hardware when it’s available. And screens are only moving toward 4k and higher (6k or 8k).
Or that GNU updates a policy that will very rapidly go from probably net silly/mildly contestedly useful to completely ridiculous in a year or two. Not allowing LLM code will be basically turning down the work of the worlds best programmers running at 50x speed in couple years, and will functionally doom any software project that enforces such a policy.
I built a GPU back end for Emacs
51–60 of 117 posts
Re: I built a GPU back end for Emacs
#52This is outstanding, if I have time I'll be switching over today. This is the kind of thing that could drive a truly free fork of emacs forward, it's enough better on realistic desktop displays to rally around and as the parent discovered "Free Software" at this point has very little to do with the freedom to do what I want on my computer in a low friction way: an ideological position on "GPUs" as a category is bizar…
> In the age of machine assist emacs could get a modern fast/cachable build, clean under all the sanitizers, io_uring on Linux, deterministic clang formatting, compat break with zero-use junk from the 80s, WASM compilation for polyglot extension (I like lisp but I understand why some people don't), modern networking, modern chrome, 100% vscode compatible LSP, modern theming that defaults to something that doesn't dri…
Re: I built a GPU back end for Emacs
#53Re: I built a GPU back end for Emacs
#54Earlier quoted context omitted.
FWIW no one can tell anymore. Claude stopped doing all the LLM ticks like 6 months ago. There's a whole industry of people trying to detect LLM writing and they're getting stomped, this can be and is extremely well studied in the literature. The criticism is that you did something wildly ambitious and pulled it off. The blog is just well written.
People clearly can, though, because they did.
More broadly, I'm just getting tired of the low effort snark on this. If someone is going to cite a passage, or examples of a theme, do some serious analysis by all means. I'm not trying to tone police high effort comments.
But this drive by "that's LLM output" thing is the new low effort "javascript is just as hard as c++" a.k.a "i don't know how to do that and i have no intention of learning and it feels bad so i'm going to lash out".
Make a case that something is deficient on its merits or don't, but baseless accusations of dishonesty are not a reasonable default. The parent here did real work that no one paid them to do, donated it to the community asking nothing in return, it's meticulous and high value, and they've already been run over by the FSF goons, you really want to pile on with no evidence?
Re: I built a GPU back end for Emacs
#55Re: I built a GPU back end for Emacs
#56Re: I built a GPU back end for Emacs
#57Re: I built a GPU back end for Emacs
#58Earlier quoted context omitted.
Very much this. I really dislike the somewhat corporate and characterless sounding tone of AI. I really liked the part where he tried to get it into upstream emacs, most of these type of projects never even get there. But yeah things like "bring honest numbers" sounds just weird.
Please, have some mercy, English is not my first language! Thanks for the advice, I'll keep it in mind.
Re: I built a GPU back end for Emacs
#59Aside from the wonderful contribution to Emacs, I have the utmost respect for how straight-forward you were with the 100% LLM generated code. The enlightening conversation on GPU freedom that ensued was also informative.
Re: I built a GPU back end for Emacs
#60Emacs user for >32 years now. It's a pity this won't get merged. There is a big usability/accessibility factor to consider here: I really wish I could have something like the Ghostty cursor_blaze.glsl shader for highlighting where the cursor is when you switch windows/buffers/apps. Most people think GPU equals silly toys like video in a text window, but there is much more to it than that. [and yes, I know about beaco…
Emacs has had this for decades: `pulse.el`. And building your own is very simple also.
You'll still need someone to write the glue code to trigger the pulse, but then a gpu patch on the backend wouldn't give you that either.
I'm sure someone on MELPA/Github has written code to do just this already.