
Let's prototype a JavaScript JIT compiler!
About this video
Andreas Kling live-codes a prototype JavaScript JIT compiler for the LibJS engine used in SerenityOS and Ladybird. He builds a standalone bytecode VM, a simple interpreter, and then a simple JIT in about 80 minutes.
Why it appears in the archive
HN commenters cite it as a concrete example of how a skilled developer uses Copilot, mostly as fancy autocomplete for codebase-specific work.
AI-generated summary and labels from the source dataset; verify important details against the video. Source & credits.
From the Hacker News discussion
The stuff Copilot helps me with is not the stuff SO could help me with. Check out 6:05 and 6:25 in this Andreas Kling video: [VIDEO] That's where Copilot shines, not for locating and copypasting answers from Stack Overflow.
Read original comment ↗> The code is usually the same code I'd get a few web searches away My impression is that people normally don't use Copilot as a substitute for finding solutions (ChatGPT is much better for that), but as a way to help with otherwise tedious tasks that are really specific to your codebase. Check out 6:05 and 6:25 in this Andreas Kling video for a good example: [VIDEO] Regarding your second point Copilot helps me when I least expects it. I think the video illustrates what I mean with that as well.
Read original comment ↗Ladybird is 425k LOC. Chromium is 3.5m LOC. Starting a new browser, using LLMs... Is not going to maintain enough context. Whilst Andreas does use Copilot a fair bit [0], he tends to do a line at a time, frequently disagree and rewrites his own, before prompting again. That is... He basically uses it as a fancy autocomplete. Not much else. [0] [VIDEO]
Read original comment ↗> Check out 6:05 and 6:25 in this Andreas Kling video for a good example: [VIDEO] Oof. So not only was it a poor replacement for a macro, it didn't even generate the correct code!
Read original comment ↗