@vercel. @v0, @nextjs, @aisdk, Satori, SWR. Don’t talk unless you can improve the silence.

We migrated mercedesamgf1.com with as little intervention as possible, setting out to prove just how much faster @vercel is. ~70% faster builds and ~75% faster paints. We derived two AI skills from the migration that we'll be sharing back. It was a mature workload with a lot of "$formerProvider-isms", and yet the net of the work was done in under a week. If it's [built / rendered / shipped] fast, it's on Vercel.
If it's fast, it's on Vercel. We just made @MercedesAMGF1 even faster. Live at mercedesamgf1.com
66
19
608
135,565
HTML/CSS is Turing complete, so why not compile programs to plain HTML/CSS and runs with zero bytes of JavaScript? zero-js.vercel.app
39
77
1,397
107,222
(How to center a DIV without JS)
1
2
34
5,351
This continues my school project from 11 years ago, just for fun: github.com/shuding/css-compu…. It's like shader code on an analog computer: no persistent state, just circuits of CSS math that react live to their inputs. Scroll-position hacks can persist state, but it's still rough.
1
1
46
7,653
After one week, there are 5 more small models for specific tasks on the web: 1. gpu-time: natural language to JS date and time by @imarikchakma 2. gpu-query: natural language to structured filters by @cheatyyyy 3. neural-flexbox: model to centre a div (!) by @aaronvanston 4. gpu-cron: natural language to cron expressions by @ManuSchiller 5. tinysarf: arabic morphological analyzers by @Ahmedabdou1996
I trained a small model to do syntax highlighting in the browser with GPU. Meet gpu-lexer from Vercel Labs: Small (27.5KB), fast (runs on WebGPU), and language-agnostic (model guesses the syntax). gpu-lexer.vercel.app It is experimental and built for learning!
24
34
688
52,079
Tiny models in the browser running on WebGPU are fun! Infer cron expressions from english language: gpu-cron.vercel.app 35k Parameters, trained with MLX, shipped as packed 6-bit weights + specialized WGSL: 31kb brotli thanks for the idea! @shuding @imarikchakma
2
4
2,066
Astra and I built Tinysarf: tiny, in-browser arabic morphological analyzers. It can segment arabic MSA words, extract roots, and other morph features ~245KB int8 weights. Runs in your browser on CPU ir WebGPU. Experimental & opensource. tinysarf-lab.ahmedabdouuu.ch…
7
2,051
Excellent use case, excited to see more gpu-* libs!
Introducing gpu-time ⏰ I built a small browser-based model to convert from natural language text to JavaScript date and time. It runs on web GPU. It's fast and can extract date and times from any English text. gpu-time.arikko.dev/
2
8
531
58,755
Got a lot of attention for this (thank you!), but also there're some criticisms and questions: 1) it's a stupid idea Maybe. Again, this is experimental and not meant to be used in production or as a replacement for anything. It is to explore new possibilities. 2) it's unnecessary and sometimes wrong Existing solutions are not always more correct just because they're "algorithmic". For example pic 1 is Highlight.js and 2 is gpu-lexer, lang is JS not something rare. There are counterexamples too. Furthermore, language-agnostic is the real reason for exploring this approach. During training, the neural network learned patterns like "[keyword] variable = value" that are not tied to any specific programming language such as: var ... = ... let ... = ... const ... = ... using ... = ... val ... = ... auto ... = ... type ... = ... def ... = ... And that knowledge can be shared without re-implementing a grammar rule repeatedly. Another advantage is that this approach can potentially generalize to new programming languages or dialects without requiring extensive manual rule creation. If you go to prismjs.com/test, you can't find popular Web framework languages like Vue, Svelte, Astro, and many others. Not to mention that new languages and dialects are constantly emerging, making it impractical to maintain comprehensive grammar rules for all of them. When that's a concern, you either use more comprehensive solutions like Shiki with a cost (carefully bundle, detect and load language definitions on demand, larger size), or use an easier approach for all kinds of source code with another cost (less accurate). That is definitely a good reason to explore this direction.
I trained a small model to do syntax highlighting in the browser with GPU. Meet gpu-lexer from Vercel Labs: Small (27.5KB), fast (runs on WebGPU), and language-agnostic (model guesses the syntax). gpu-lexer.vercel.app It is experimental and built for learning!
23
6
273
29,458
Another thought: if you see each part (a word, symbol, number, space) of the source code as a pixel, syntax highlighting is essentially image segmentation for a 1D image. And it's a well-solved problem by models.
2
1
42
3,257
I trained a small model to do syntax highlighting in the browser with GPU. Meet gpu-lexer from Vercel Labs: Small (27.5KB), fast (runs on WebGPU), and language-agnostic (model guesses the syntax). gpu-lexer.vercel.app It is experimental and built for learning!
148
288
3,988
795,719
Correctness. I’m comparing every span types with Shiki, which is almost the golden standard today. It shows the weighted correctness of top 25 popular languages on GitHub. Shiki uses real AST while others might not, hence the differences.
2
80
14,238
Why creating this? I’ve been struggling with syntax highlighting for years mostly because: 1) large language grammar bundles; 2) language detection and dynamic loading; 3) bad perf and slow down of main app. And it’s great to explore more possibilities and share!
6
125
12,271
13 years ago, Apple asked a question that hits me harder today than ever: If everyone is busy making everything, how can anyone perfect anything? Every day, I see a world flooded with effortless AI slops. I’m realizing that to build something truly great today, you need a level of focus the world has never demanded before. It feels like trying to write a quiet, beautiful song in a room full of loud noise.
105
472
3,940
139,257