Janis Jansen 🌳

The game Metroid Fusion (the best Metroid game) and a Wii remote.

You can't stop me from playing Metroid Fusion on a GBA emulator on my modded Wii.

I do own a computer and I do own several other consoles. But this is the way you are supposed to play GBA games.

Crazy how consistent that is! My three user apps could never.

Should we remove XSLT from the web platform? · Issue #11523 · whatwg/html What is the issue with the HTML Standard? XSLT v1.0, which all browsers adhere to, was standardized in 1999. In the meantime, XSLT has evolved to v2.0 and v3.0, adding features, and growing apart f...

And also
github.com/whatwg/html/...

I didn't even know browsers support it at runtime?? Thought it needed to be processed beforehand.

For people like me who need to read up, here is a discussion on the deprecation in blink
groups.google.com/a/chromium.o...

"This is a classical issue when <some activity Claude absolutely has no clue about AT ALL"

Awesome, great to know!

The part I felt was "dirty" was me writing some regex which might or might not work. As soon as I write regexes, I feel like I shouldn't have. But providing paths like you mentioned feels better :)

Okay sorry for the spam, but I'm stupid. You can filter by regex.
`-regexp:/(src|node_modules|@vite)` kinda hides all these requests in a very dirty way.

(I tried to just set a custom response header like "Vite-hide-request", but they're not added to all responses)

Though I feel like that's something other people already have figured out? @jakearchibald.com maybe you know how to get rid of unwanted dev server requests in the network panel, for example requests for @vite.dev modules.

You can filter by domain and negate, but that would hide too many

In Firefox, if you could filter network requests based on path/file.. you could negate the filter and exclude all requests from the vite dev server.

I think that's something we need. Vite module requests always spam the network panel.

"... and that concludes our guide to using the ECMAScript language effectively.

Now, forget everything you just read and let's talk about nodejs."

I also hate that you can use either asterisks, dashes OR underscores to make horizontal lines.

We recently needed to adjust how we parse markdown because we had messages that were "censored" with asterisks, which were interpreted as lines.

It's like working with a technology for 10 years and then learning in random bluesky comments, that you always used a part of it fundamentally wrong without noticing.

The amount of specs, exceptions and precautions to ensure compatibility and graceful handling is just insane.

Wow. For some reason I never realized vitest used chai. Makes absolute sense, but I always assumed vitest built its own assertions with a chai-like API.

Anyways, great to hear about the improvements!

Hm yeah might be. I did struggle especially with audio as soon as I wanted something non-standard. Like low level audio device access for DAWs, or getting my shitty audio card to work. But it was fun in a weird way.

Screenshot of a GitHub PR summary, showing: 162 Files changed, +11.691 additions, -2.682 deletions and 24 commits

We're getting there! Was a very productive week.

I mean sure you can figure it out. And once it's set up fully, it's super awesome.

But I already don't want to deal with, idk, audio tool chains and graphics drivers etc. on mainstream Linux, let alone on nixOS.

Yggdrasil Web site: sunsite.unc.edu/Sep-29-1996/docs/distributions/yggdrasil/announcement (not active) Origin: USA Category: Desktop Desktop environment: GUI ? Architecture: x86 Based on: Independent Wikipedia…

Not gonna lie, I'm this 🤏 close to diving down the "Yggdrasil Linux" rabbit hole. But I will resist. Can recommend the Wikipedia entry and this post though.

archiveos.org/yggdrasil/

"What Linux distro are you using?"
"I'm rocking plug-and-play Linux"

It's simple for a developer with 15 years of Linux experience. Difficult for the remaining 8.1 billion.

Let an LLM write some code. Then write like 100 tests but still don't trust the code.

- coding in 2025

Wow. fully forgot I pre-ordered that. Congratulations to all of us then!

I think more people should

(that's excluding all media query level 5 ones btw, they're even more that I will hide behind a flag because of browser support)

| `-webkit-${string}` | `-moz-${string}` | `-ms-${string}` | `-o-${string}` | `-khtml-${string}` | `-apple-${string}` | `-x-moz-${string}`;

Speaking of Vendor prefixes. These are the ones I found so far

Stopping with the "spam" now :) sorry

":dir" | ":has" | ":host" | ":host-context" | ":is" | ":lang" | ":not" | ":nth-child" | ":nth-last-child" | ":nth-last-of-type" | ":nth-of-type" | ":where" | ":active" | ":any-link" | ":blank" | ":checked" | ":current" | ":default" | ":defined" | ":disabled" | ":empty" | ":enabled" | ":first" | ":first-child" | ":first-of-type" | ":focus" | ":focus-visible" | ":focus-within" | ":fullscreen" | ":future" | ":hover" | ":in-range" | ":indeterminate" | ":invalid" | ":last-child" | ":last-of-type" | ":left" | ":link" | ":local-link" | ":nth-col" | ... 21 more ... | ":visited"

"::cue" | "::cue-region" | "::part" | "::slotted" | "::view-transition-group" | "::view-transition-image-pair" | "::view-transition-new" | "::view-transition-old" | "::after" | "::backdrop" | "::before" | "::first-letter" | "::first-line" | "::grammar-error" | "::marker" | "::placeholder" | "::selection" | "::spelling-error" | "::target-text" | "::view-transition"

I also got one for (I hope) every single pseudo class and pseudo element!

There are some edge-cases though. like `:matches()`. And it excludes vendor-prefixed ones. Couldn't be bothered.

Here you go. All 40 of them: 'any-hover', 'any-pointer', 'color-gamut', 'grid', 'hover', 'overflow-block', 'overflow-inline', 'pointer', 'scan', 'update', 'aspect-ratio', 'color', 'color-index', 'device-aspect-ratio', 'device-height', 'device-width', 'height', 'monochrome', 'resolution', 'width', 'max-aspect-ratio', 'max-color', 'max-color-index', 'max-device-aspect-ratio', 'max-device-height', 'max-device-width', 'max-height', 'max-monochrome', 'max-resolution', 'max-width', 'min-aspect-ratio', 'min-color', 'min-color-index', 'min-device-aspect-ratio', 'min-device-height', 'min-device-width', 'min-height', 'min-monochrome', 'min-resolution', 'min-width'

I'm learning so much more about CSS by building surimi (because I am forced to read the CSS specification).

For example, just wrote some types to figure out all possible @media query descriptors you can use.

It's 40 in total

Is the part you've already done open source? 🌚

Awesome! Have fun :)

I'm in a deep `extends...infer` typescript hole again. And it's just awesome. Getting a lot done today!