Janis Jansen 🌳
@janis.me
Putting things on websites you didn't know could be on websites. Like fluid simulations or CAD software. Also conversational AI agents at cognigy.ai. Currently working on surimi.dev (pre-alpha)
🔗 janis.me
🖥️ github.com/janis-me
📽️ youtube.com/@janis-me
🔗 janis.me
🖥️ github.com/janis-me
📽️ youtube.com/@janis-me
Crazy how consistent that is! My three user apps could never.
November 4, 2025 at 7:18 AM
Crazy how consistent that is! My three user apps could never.
And also
github.com/whatwg/html/...
github.com/whatwg/html/...
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...
github.com
November 1, 2025 at 3:49 PM
And also
github.com/whatwg/html/...
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...
For people like me who need to read up, here is a discussion on the deprecation in blink
groups.google.com/a/chromium.o...
Intent to Deprecate and Remove: Deprecate and remove XSLT
groups.google.com
November 1, 2025 at 3:47 PM
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...
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"
October 31, 2025 at 1:23 PM
"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 :)
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 :)
October 28, 2025 at 10:10 AM
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 :)
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.
`-regexp:/(src|node_modules|@vite)` kinda hides all these requests in a very dirty way.
October 28, 2025 at 6:43 AM
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.
`-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)
October 28, 2025 at 6:37 AM
(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
You can filter by domain and negate, but that would hide too many
October 28, 2025 at 6:34 AM
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
You can filter by domain and negate, but that would hide too many
"... and that concludes our guide to using the ECMAScript language effectively.
Now, forget everything you just read and let's talk about nodejs."
Now, forget everything you just read and let's talk about nodejs."
October 26, 2025 at 5:43 PM
"... and that concludes our guide to using the ECMAScript language effectively.
Now, forget everything you just read and let's talk about nodejs."
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.
We recently needed to adjust how we parse markdown because we had messages that were "censored" with asterisks, which were interpreted as lines.
October 26, 2025 at 5:22 PM
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.
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.
The amount of specs, exceptions and precautions to ensure compatibility and graceful handling is just insane.
October 26, 2025 at 5:18 PM
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.
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!
Anyways, great to hear about the improvements!
October 26, 2025 at 5:14 PM
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!
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.
October 24, 2025 at 8:16 AM
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.
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.
But I already don't want to deal with, idk, audio tool chains and graphics drivers etc. on mainstream Linux, let alone on nixOS.
October 23, 2025 at 8:08 PM
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.
But I already don't want to deal with, idk, audio tool chains and graphics drivers etc. on mainstream Linux, let alone on nixOS.
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/
archiveos.org/yggdrasil/
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…
archiveos.org
October 23, 2025 at 8:03 PM
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/
archiveos.org/yggdrasil/
"What Linux distro are you using?"
"I'm rocking plug-and-play Linux"
"I'm rocking plug-and-play Linux"
October 23, 2025 at 7:58 PM
"What Linux distro are you using?"
"I'm rocking plug-and-play Linux"
"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.
October 23, 2025 at 7:56 PM
It's simple for a developer with 15 years of Linux experience. Difficult for the remaining 8.1 billion.
Wow. fully forgot I pre-ordered that. Congratulations to all of us then!
October 23, 2025 at 11:12 AM
Wow. fully forgot I pre-ordered that. Congratulations to all of us then!
I think more people should
October 22, 2025 at 4:45 AM
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)
October 20, 2025 at 1:12 PM
(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)