Live data from Hacker News

How to build a diffusion language model

kuleshov-group.github.io

21–23 of 23 posts

Re: How to build a diffusion language model

#21

Something I've wondered, maybe I should just do it if I can find some time, but... given DeepSeek's nice results on using rendered text as input, I'm wondering if anyone has given serious research efforts towards image-based diffusion methods for text. As in, instead of all the complexities induced by discrete token generation, just generate the image of the text using standard image diffusion methods, then convert i…

[deleted]

Re: How to build a diffusion language model

#22

This should be much more efficient in theory, right? Why dont we see more leading labs adopt this?

Google was at least trying. Wouldn't be surprised if the others were experimenting with it too. The bar is going to be a lot higher now for for any diffusion model to go from experiment to product since it needs to compete with stuff like glm 5.3 flash and Luna on cost/efficiency for a given quality of output, which is not going to be easy. If it was easy Gemini diffusion would have landed - if it requires a bunch of money and effort it has a much higher bar to make it to market, if it requires some clever breakthrough you have no way of knowing where that's going to come from or what it'll look like/if it'll even seem important when it happens

Re: How to build a diffusion language model

#23
post #12

Earlier quoted context omitted.

Could be! I have not (yet) spent much time learning about how llms work, just the occasional blog here and there. My main question is why we _need_ a bit of additional code to massage the input into tokens and especially why the neural network cannot do it, i.e., let the embedding be a latent space that forms naturally when training the network. If that makes sense.

“let the embedding be a latent space that forms naturally when training the network” The embeddings are produced in concert with the network, to serve the network, and not created as a separate step. It’s actually very cool The look-up table is a matrix. Each row is an embedding and each row number is a token ID. You get a differentiable transformation from token ID to token embedding using a “one hot vector” and a m…

I'll have a look at that paper, thanks!
Post reply on HN