UEFI Bindings for JavaScript • Hacker News Board

my_throwaway23 wrote: post #14

I presume you'll add the network stack next, so that I can use my favourite, most useful packages? import isOdd from "https://unpkg.com/is-odd";

Well, there's a network stack already there, including HTTP and HTTPS on newer firmwares.

Re: UEFI Bindings for JavaScript

#26

Post by aruametello » Mon, Feb 09, 2026, 3:13 PM UTC

redvulps wrote: post #12

next step is to create a UEFI TUI using react (please don't)

you may just have casted a curse on our future motherboards, damn you

Re: UEFI Bindings for JavaScript

#27

Post by spiffyk » Mon, Feb 09, 2026, 3:17 PM UTC

monax wrote: post #17

my_throwaway23 wrote: post #14

I presume you'll add the network stack next, so that I can use my favourite, most useful packages? import isOdd from "https://unpkg.com/is-odd";

We are getting isOdd in the bootloader before GTA-IV

Wait, when did I time-travel?

Re: UEFI Bindings for JavaScript

#28

Post by ThrowawayTestr » Mon, Feb 09, 2026, 3:18 PM UTC

madduci wrote: post #3

But why?

Why not?

Re: UEFI Bindings for JavaScript

#29

Post by nxobject » Mon, Feb 09, 2026, 3:20 PM UTC

monax wrote: post #19

catapart wrote: post #15

Can someone break this down for me? Looks like it's using... C? to load a js interpreter which bootstraps an API around all UEFI features? Do I have that right? And, if so, does that mean that once the API has been bootstrapped, one could actually write an OS in js? Or are there other abstractions that would need to be migrated first?

Depending on your definition of OS, yeah you could do that :)

Hey, when Apple transitioned from m68k to PowerPC, it took them a hell of a long time to rewrite massive parts of their OS. It's a low bar, though...

Re: UEFI Bindings for JavaScript

#30

Post by lioeters » Mon, Feb 09, 2026, 3:21 PM UTC

Turning in the widening gyre, the falcon cannot hear the falconer. The center cannot hold.. The old prophecy is coming true.