Years ago, long before the current "AI"/LLM-craze, I've heard someone saying that in the future programming will have less fixed, deterministic algorithms and more statistical/ML algorithms, because even in the case when writing a deterministic algorithm is possible, it is sometimes easier to collect training data and train a tiny model, then to write and maintain large codebase that does the same thing, but deterministically.

I wonder, if mass adoption of LLM code-generation will accelerate this process or not. On the one hand, it is now easier to "write" (LLM-generate) code then ever, so time/effort savings are not there anymore (probably, I'm not sure). On the other hand, now everyone uses LLMs so, I think, people are less deterred by non-determinism and statistical nature of ML models.

Let's imagine that you are making a CLI tool. What does a CLI tool do? Well, it accepts reads arguments, reads stdin, writes stdout and make syscalls. So, all possible inputs and outputs are very well defined. What if in the future it will be easier (and maybe even more natural) to ask an LLM to "imagine" tons of possible inputs and correct outputs for a tool that you are making and then train a tiny model, without writing or generating any code?

• weinzierl

  today at 8:11 AM

  "the future programming will have less fixed, deterministic algorithms and more statistical/ML algorithms"

  I think the direction this will be going depends in part on how hardware prices will develop. If we continue with "hardware is cheap, don't think about it" like we did in the past decades I can see this happen. On the other hand, if we continue down the path we've recently taken, people who know when to choose which approach to their advantage will have a good and prosperous life.

A genuinely impressive and novel use of machine learning? In this economy?

Looks really impressive, although one issue I do see is consistency. For example, it seems to highlight `null` as a value, unless it is on the left side of an `===` expression, since it probably hasn't seen that in training.

Was it ever actually tested on languages not in the training set? Would be interesting to see if a model this small can actually generalize...

27 KB is extraordinarily impressive. Here's a deterministic suite of common language- and format-specific PHP files an LLM wrote for me in 32 KB, for comparison:

https://repo.autonoma.ca/repo/treetrek/tree/HEAD/render/rule...

I think what's most interesting is not that this works well for common languages, but it seems to be useful for languages that don't exist yet. If you want _some_ highlighting for your SQL variant, or your language that borrows many common idioms, or just sloppy code that's close enough to the target language, this could be useful.

On linux (tried FF and chromium), the live demo renders all the text as black (no highlighting). On iOS (my phone), this works great. No errors in the console (maybe it fails silently?)

Is this a linux issue / support issue?

• vova_hn2

  today at 8:06 AM

  I think, both FF and chromium on Linux disable WebGPU by default. Of course, it depends on where exactly did you get it (what kind of default settings people that packaged it for your distro used).

  Just look up "<browser name> enable webgpu" in you favorite search system or ask an LLM chatbot "How to enable WebGPU in <browser name>?", follow the instructions and it should work just fine.

• aitoolsprimer

  today at 5:11 AM

  Check navigator.gpu in the console on the Linux machine. If it is undefined, that is your answer, and it explains the silence: the page has no API to fail against, so nothing throws.

  WebGPU on Linux is still the exception, not the rule. Firefox ships it enabled by default in Nightly only, not Stable or Beta, with Linux expected during 2026. Chrome enables it by default on Linux only for Intel Gen12+ (from 144) and NVIDIA with driver 535.183.01+ on Wayland (from 147); everything else is behind flags, roughly --enable-unsafe-webgpu --ozone-platform=x11 --use-angle=vulkan --enable-features=Vulkan,VulkanFromANGLE. Distro Chromium builds also differ from Google Chrome here more often than people expect.

  Which matches what you saw exactly: works on iOS, black text on both Linux browsers, clean console. Worth the demo printing a one-line "WebGPU unavailable" instead of rendering black on black, because right now a missing API and a broken shader look identical from the outside.

If anyone can get in contact with Shu, please let them know I'd really like to speak with them. I have a deterministic rendering / colorizing system in three dimensions instead of two for arbitrary UTF8 text written that is explicitly GPU bound and currently testing the last Rust + Mojo pair port, and I'd like to share some ideas. I have about 95 million glyphs rendering (monospace, atm) in a little under a second with full multi dimensional pagination and colorizing per-glyph with full addressing capabilities. There's something to be combined with these two mechanisms I'd like to try and explore.

• tough

  today at 4:20 AM

  g@shud.in was listed as contact email on his older portfolio

nice, a tiny webgpu model instead of a grammar is such a clean idea. how does it hold up on languages with really

This is a tiny LLM doing all the heavy-lifting. Any mention of the training process? I am obsessed with tiny LLMs and the do-one-thing-really-well approach that they seem to fit very well.

I don't think it's meant as something that's useful per se because highlighting 5m lines of code at once is unusual, and doing it in a non-deterministic way probably isn't especially helpful, but to show what a browser is capable of it's awesome.

• michaelt

  today at 6:06 AM

  > highlighting 5m lines of code at once is unusual

  Speak for yourself, I often accidentally open 50MB JSON files, crashing my text editor as it tries to figure out the syntax highlighting :)

  • silon42

    today at 6:53 AM

    50MB in one line (with syntax highlighting) is a good test of a text editor.

• avaer

  today at 3:14 AM

  The use case isn't highlighting a huge amount of code, but local re-entrant highlighting.

  You generally never need to highlight a whole file, only the part you're looking at. Which by definition must be fuzzy since you don't have the full source, the part you see will not parse as a complete program so you need to guess. This is actually one of the nastier parts of writing a highlighter, and it must be done for every language.

  The lesson is that if you're going to be fuzzy you might as well be learned too and the results are pretty good.

  This is more useful than it appears at first glance. It would be just as useful running on the CPU, which I'm sure it can.

  • umpalumpaaa

    today at 3:47 AM

    Is that really the use case for the related packages mentioned on their website? highlightjs and prismjs are typically used to highlight code snippets on websites… which are at most a few hundred lines long. And are usually highlighted as a whole

    • tough

      today at 4:24 AM

      you have to bundle and ship per language syntax dictionaries tho

  • silon42

    today at 7:03 AM

    No need to guess... For basic system highlighting, one can store the lexer context periodically (maybe per line) and invalidate it if edits are made before it. For more advanced stuff, you need a more complete parser anyway and do it asynchronously (LSP...).

    • vidarh

      today at 7:36 AM

      That is a good optimization, but you still need to figure out the starting state at a given location, and for quite a lot of languages that is not solvable in the local case.

      E.g. if you're looking at a page of Ruby, you can not in the general case know if it's inside or outside a quoted string, as the quote character can be any arbitrary character (and I really mean any. "% x " excluding the double-quotes is a valid Ruby quoted string where the quote character is space but you can e.g. pick a unicode codepoint you're not going to use anywhere else in the file)

      So unless you parse from the start of the file, you're left with fuzzy matching, and that can be made good enough the vast majority of time.

  • normie3000

    today at 3:38 AM

    > the part you see will not parse as a complete program so you need to guess

    Presumably this could also be a useful trait when live highlighting of files when editing, as in-progress typing is likely to be unparseable sometimes.

"27.5KB" will not age well.

But what could I expect from another vibe coded project?

Does this do the tokenization? Could it be expanded to parse the whole structure of the language?

Seems don't work on firefox mobile on Android

• hmry

  today at 2:50 AM

  Firefox Android doesn't support WebGPU yet

> 95–100% agreement for actionscript

Great news for a language whose last stable release was 20 years ago