iiinova — where your digital self keeps evolving

No, personally I only use dark mode. But others do, and the dark mode experience suffers because of it. Many websites I visit are bright and hurt my eyes on first visit, even if they have a dark mode toggle.

010

Remco Haszing @remcohaszing.nl · 12h

The hardest thing is that there’s no proper toggling support. All current approaches are hacky. Browsers need to support the user preferences API.

developer.mozilla.org

User Preferences API - Web APIs | MDN

The User Preferences API allows page authors to programmatically override user preference-related media query settings.

140

Remco Haszing @remcohaszing.nl · 16h

Nice! I know of some projects that could use a logo. I would love to see icons for dprint.json or Herebyfile.js, but they have no logo.

000

Remco Haszing @remcohaszing.nl · 22h

Yeah, I try to avoid Slack. It has the most confusing account management I’ve ever seen, as well as some other quirks.

020

Reposted by Remco Haszing

Kilian Valkhof @kilianvalkhof.com · 29/09/2026

IT HAS DARK MODE

Two panes showing the new example.com, one in light mode and the other in dark mode

191

Remco Haszing @remcohaszing.nl · 27/09/2026

Well that’s inconclusive 😅

Activity close to automation signals.

Mixed activity

Activity patterns show a mix of organic and automated signals.

Analyzed from the last 80 public GitHub events

110

Remco Haszing @remcohaszing.nl · 27/09/2026

I recall someone wrote a tool to see if a GitHub account it a slop bot or not. What’s the name / link of the tool again?

100

Remco Haszing @remcohaszing.nl · 27/09/2026

The ice caves look so cool! 🥶

010

Remco Haszing @remcohaszing.nl · 25/09/2026

I like the “Human Responsible” one, except I feel like AI disclosure should be required, not forbidden. I don’t care which one or how, only that you disclose it.

040

Remco Haszing @remcohaszing.nl · 25/09/2026

Cool! My first security advisory from a third party for one of my personal projects! Oh wait… it’s LLM spam from a new GitHub account

160

Remco Haszing @remcohaszing.nl · 25/09/2026

I look forward to the changes it brings for Vitest users! 😀

110

Remco Haszing @remcohaszing.nl · 25/09/2026

I hear you, but know that there are still people who care. We’re all in this together.

141

Remco Haszing @remcohaszing.nl · 24/09/2026

Indeed. But it’s still the right thing to do, no matter the tool.

010

Remco Haszing @remcohaszing.nl · 24/09/2026

This also means you deserve both blame and attribution for the change. And it’s also your job to give proper attribution if the code was copied from somewhere else.

2100

Remco Haszing @remcohaszing.nl · 24/09/2026

LLMs are tools, not people. This means they are not authors either. They are not the author of your git commits, you are. It’s good to disclose if you used an LLM to make edits, but the commit author field is not the right place. That’s just a weird place to put an ad for the tool.

1275

Remco Haszing @remcohaszing.nl · 23/09/2026

Some of these changes have even veen merged and released already. But they tend to appear under the “Thank you” section of the release notes, so they’re not as prominent as the highlights.

120

Remco Haszing @remcohaszing.nl · 23/09/2026

I still have some exciting human experience VSCode features locally! I just need to get them into a mergable state

110

Remco Haszing @remcohaszing.nl · 23/09/2026

The most important limitation is that custom languages can’t override file extensions that are supported natively by TypeScript.

040

Remco Haszing @remcohaszing.nl · 23/09/2026

More complex languages are supported too. I made it for CSS modules, because it’s easy. I also implemented a content mapper for MDX, which is more complex. And others are working on content mappers for Astro, Ember, Svelte, Vue, and sorry if I forgot any.

130

Remco Haszing @remcohaszing.nl · 23/09/2026

I’m surprised how fast you added not just content mapper support, but even support for plugins of a specific content mapper.

120

Remco Haszing @remcohaszing.nl · 22/09/2026

When TypeScript 7.1 is released. Until then, the protocol used could still change (although that chance decreases every day). You also need to build the VSCode TypeScript extension from source to use content mappers for now. That having said, I definitely welcome feedback.

github.com

Provide TypeScript 7.1 content mapper · Issue #533 · mdx-js/mdx-analyzer

TypeScript introduced the new content mapper API in microsoft/typescript-go#4712. This will be released in TypeScript 7.1. I built mdx-content-mapper as a proof of concept and to provide feedback t...

020

Remco Haszing @remcohaszing.nl · 22/09/2026

It’s not just eye strain or headaches. If you have damage to your eye, light sources can feel like physical pain to your eyes directly.

010

Remco Haszing @remcohaszing.nl · 22/09/2026

Doesn’t Windows have some sort of equivalent? Or otherwise maybe ship man pages rendered to HTML for Windows. Man pages feel so sensical to me, I didn't even occur to me that could cause cross platform compatibility issues.

000

Remco Haszing @remcohaszing.nl · 22/09/2026

I made some significant changes to mdx-content-mapper. It now uses micromark tokens instead of mdast. This makes the mappings much more stable and gives better handling if certain syntax errors. But my cat won’t allow me to move off the couch, so I won’t make a release today.

120

Reposted by Remco Haszing

Cynthia 🐈 @cynthia.dev · 22/09/2026

new smol-toml release who dis - Full Temporal support - 2x performance improvements - New options for safe handling of `__proto__` - Lots of correctness fixes and additions github.com/squirrelchat...

github.com

Release v1.9.0 · squirrelchat/smol-toml

Huge update!!! This is most likely the largest update the library received since its release, with lots of new features and improvements. Performance improvements Significant parts of the internal ...

251

Remco Haszing @remcohaszing.nl · 22/09/2026

I’m surprised to see the addition of a null prototype improves performance. I had the same idea earlier for a YAML parser, but it was pointed out to me this is actually less performant in many cases.

100

Remco Haszing @remcohaszing.nl · 22/09/2026

I’m surprised he doesn’t call it American Intelligence

070

Remco Haszing @remcohaszing.nl · 21/09/2026

I think a man page would be the right place for this

100

Reposted by Remco Haszing

Artem Zakharchenko @kettanaito.com · 21/09/2026

This is such a silly mistake and yet I see you making it all the time in your tests. ❌ Do NOT run cleanup after assertions ✅ Schedule the cleanup via hooks or use Disposable Objects A seemingly tiny change that'll have tremendous impact on your tests, especially memory-wise.

Code snippets illustrate proper and improper cleanup methods for WebSocket tests, emphasizing memory management in asynchronous operations.

2364

Remco Haszing @remcohaszing.nl · 21/09/2026

True. I wasn’t sure if you parsed the format beforehand.

010

Remco Haszing @remcohaszing.nl · 21/09/2026

There’s also the `Temporal.Instant` constructor, but it’s not as widely supported.

110

Remco Haszing @remcohaszing.nl · 20/09/2026

This is what "prepack" is for.

000

Remco Haszing @remcohaszing.nl · 20/09/2026

I don’t think what people should use really changes. Instead I think there are a lot of uninformed recommendations out there.

100

Remco Haszing @remcohaszing.nl · 20/09/2026

"prepack" happens before packing. This is where your build script should go. "prepublishOnly" happens before publishing. I can’t think of any use case for that. "dependencies" runs if `npm install` changes your node_modules. This is the right place for something like "husky". It’s a bit more niche

210

Remco Haszing @remcohaszing.nl · 20/09/2026

Pathfinder 2 Hexquest (made by a friend of mine) Forbidden Lands Mörk Borg If Mörk Borg taught me anything, it’s not to trust anyone. I don’t believe you’re a cop.

110

Remco Haszing @remcohaszing.nl · 20/09/2026

Yeah, "prepack" is the way to go. I just see it relatively little in practice. And sometimes people actually meant to use "dependencies" instead of "prepare".

010

Remco Haszing @remcohaszing.nl · 20/09/2026

Lol, that bicycle chained above the water is very Dutch

030

Remco Haszing @remcohaszing.nl · 20/09/2026

Why do people use the "prepublishOnly" and "prepare" npm script? I feel like they serve no real purpose, but people use them because they’re used and written about a lot.

300

Remco Haszing @remcohaszing.nl · 20/09/2026

This standard has been around for years, but it was only enabled by default in xdg-user-dirs recently. So I think we can expect distros anno 2027 to enable it by default.

010

Remco Haszing @remcohaszing.nl · 20/09/2026

In modern Linux environments there's a standard directory for it this named `~/Projects`.

110

Remco Haszing @remcohaszing.nl · 18/09/2026

Yep, 4 is the other one. Not what you mean with the rest 😅

000

Remco Haszing @remcohaszing.nl · 18/09/2026

Cool! Apparently my kilt fits again somehow. I guess I'm not wearing pants tomorrow

010

Remco Haszing @remcohaszing.nl · 18/09/2026

Right… that sort of makes sense I guess. In practice it just makes the AST weird

010