This became real a lot quicker than I thought 😂
There's also a talk about this tomorrow at PlanetNix!
bsky.app/profile/surm...
05.03.2026 19:46
👍 2
🔁 0
💬 0
📌 0
This became real a lot quicker than I thought 😂
There's also a talk about this tomorrow at PlanetNix!
bsky.app/profile/surm...
`builtins.wasm` is now a (experimental) thing in @determinate.systems’ nix, with a PR open for upstream nix.
This lets you extend the nix language by compiling C/C++/Rust/etc into safely sandboxed, platform-independent plugins!
determinate.systems/blog/builtin...
What a flex :D
Fwiw, it was similarly easy on the spec side. The algorithm was fully spec’d, just not attached to any globals. And after the spec was written, it took 3 years or something for browsers to go “well I suppose this is kinda useful?” 😂
do you like geology puns and have an unhealthy obsession with package management? 🌋📦
we’re building a nix-based monorepo build system (in Rust!) at Shopify and we’re hiring.
global, remote, high-autonomy. DMs open.
www.shopify.com/careers/soft...
Thank you!! Fixed :)
I have been working on the nix & Rust codebase that builds Shopify’s monorepo, and there’s so much left to do that we need help.
If you are interested, apply here to join us! DM me if you have questions!
www.shopify.com/careers/soft...
I dug into progressive image rendering and found a bunch of common assumptions aren't quite true.
➡️ JPEG & WebP progressive-renders worse in Safari
➡️ AVIF _does_ support progressive
➡️ But JPEG XL in Safari doesn't
➡️ JPEG XL decodes much slower than AVIF
⬇️ and more
jakearchibald.com/2025/present...
It can handle 400 megapixel manga like no other
JSConf.eu throwback for me
Take a look at ImHex!!
This is so perfect for you. Can't wait to see you crush it.
Alternativprojektsinterressantheitsverstärkung
`enum` yes, `const enum` no. Gotta love TS sometimes :3
You know your JS13k submission is going well when you have to resort to `btoa` and other seemingly stupid hacks to get below the file size limit.
if this type of thing makes you say “this is cursed af, where do i sign up” DM me, we’re looking for some teammates
For now, I established the convention the the parameters must be pointers to byte arrays containing UTF-8 encoded JSON strings. I think that’s actually quite feasible.
But the real deal would be to use the Wasm component model imo
Nix friends: How terrible is this idea?
I added `builtins.runWasm` to nix, allowing you to call out to Wasm. The Wasm is reset every time, so the functions remain pure. This gives you a (performant?) escape hatch for things that Nix is missing. E.g parsing YAML (here: via Rust)
📝 Making XML human-readable without XSLT.
Turns out, JavaScript works pretty well!
jakearchibald.com/2025/making-...
I guess I grouped all kinds of implementation bugs into the "interoperability" category. Probably not super fair to folks working on interop 😅
I had to learn it for my UK citizenship test. I didn't do very well, just barely enough to pass.
I mean, something working in one browser and not the other is a failure of either interoperability or specification.
The thing is that Firefox on iOS is not even Firefox. But whenever I see multiple rAF's nested, especially with a setTimeout sprinkled in, I gotta summon Jake.
@jakearchibald.com plz fix
Me, sitting behind a cuddly toy of a fox. Ok it's obviously Firefox.
Starting my new role on Monday. Could be anywhere.
![let arr = new Uint8Array([72, 101, 108, 108, 111, 32, 87, 111, 114, 108, 100]);
console.log(arr.toBase64());
// 'SGVsbG8gV29ybGQ='
console.log(arr.toHex());
// '48656c6c6f20576f726c64'
let string = 'SGVsbG8gV29ybGQ=';
console.log(Uint8Array.fromBase64(string));
// Uint8Array([72, 101, 108, 108, 111, 32, 87, 111, 114, 108, 100])
string = '48656c6c6f20576f726c64';
console.log(Uint8Array.fromHex(string));
// Uint8Array([72, 101, 108, 108, 111, 32, 87, 111, 114, 108, 100])](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:w227epg3attqnssfdkx6ex6a/bafkreihrq4aegp6a5gtlqnkcox5w6eblthyvnz66w6gf53mvuh4fsr3254@jpeg)
let arr = new Uint8Array([72, 101, 108, 108, 111, 32, 87, 111, 114, 108, 100]); console.log(arr.toBase64()); // 'SGVsbG8gV29ybGQ=' console.log(arr.toHex()); // '48656c6c6f20576f726c64' let string = 'SGVsbG8gV29ybGQ='; console.log(Uint8Array.fromBase64(string)); // Uint8Array([72, 101, 108, 108, 111, 32, 87, 111, 114, 108, 100]) string = '48656c6c6f20576f726c64'; console.log(Uint8Array.fromHex(string)); // Uint8Array([72, 101, 108, 108, 111, 32, 87, 111, 114, 108, 100])
ECMAScript excitement 😉
Congrats to @bakkot.com on advancing UInt8Array ↔️ Base64/Hex to Stage 4 at TC39 this week 🎉
UInt8Array.prototype.
toBase64
toHex
UInt8Array.
fromBase64
fromHex
It lets you convert directly between binary data and Base64/Hex strings 👍
Super happy with hyperoptic
Oh that's interesting. I wonder if this is from the merge of ChromeOS and Android.
Let me see if I can install nix :3
I spent hours and hours trawling through the sites of some of the world's best web developers, and despite the horrors I regularly experience in my daily work in Big JavaScript Territory, what I saw left me hopeful:
infrequently.org/2025/07/links/
No, I'd want `x.a` to still be an error, which would not be the case with `any`. With `?.` I feel like I'm opting in to props that TS is not aware of