Lenz Weber-Tronic
banner
phry.dev
Lenz Weber-Tronic
@phry.dev
Maintaining Apollo Client at Apollo GraphQL

Redux Toolkit Co-Maintainer
Creator of RTK Query

Some additional keywords for people to find me:
OpenSource, TypeScript, JavaScript, React

web: phryneas.de
phryneas on most platforms
@phry on the bird
This would work so nicely for typescript type narrowing.
November 10, 2025 at 8:40 PM
That's a different thing I believe. This thread is not about how long it takes until it executes, but how long scheduling a timeout blocks synchronous execution.
November 10, 2025 at 2:54 PM
Niiiice! Congrats!
November 3, 2025 at 7:39 AM
Try this website - you can upload your savegame and it'll show you what you're missing: silksong-completion.info
Silksong 100% Completion Info Save File Check Analyzer
Check your Hollow Knight: Silksong save file with 100% completion analyzer. See your exact completion percentage and get detailed checklist of every missing item shown on the map with a guide on how t...
silksong-completion.info
November 2, 2025 at 9:47 PM
Congratulations!
I'm still at 96% - that flea juggle is no as simple as I thought it would be.
November 2, 2025 at 9:43 PM
Good to know!
October 30, 2025 at 10:11 PM
Then it's probably fine :)

But for context, before seeing your answer I dug out this article which explains the problem a bit: www.regular-expressions.info/catastrophic...
Runaway Regular Expressions: Catastrophic Backtracking
This is the reason why your regular expression takes forever, or crashes your program.
www.regular-expressions.info
October 30, 2025 at 8:39 PM
So this kind of construct can explode compute time for Regexp. I'd assume similar for `${string}${string}`.
October 30, 2025 at 7:53 PM
At least for Rexexp, `.*.*x` is *very* expensive when matching something like `aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa` since first the first group will expand to the end, notice there's no `x`, then it will try to expand n-1 times and use one letter from the second group and so on.
October 30, 2025 at 7:53 PM
Fascinating! Lots of `${string}${string}` though - can you avoid that?
Just a hunch, but going from similar RegExp, it might slow down TSC a lot when trying to actually match in the end.
October 29, 2025 at 6:08 AM
I'm still hoping that JS will get whitespace-ignoring RegExp with comments - this php RegExp reads so much nicer: github.com/TBroTeam/TBr...
TBro/src/cli/import/commands/Importer_Annotations_Repeatmasker.php at master · TBroTeam/TBro
Visualization and management of denovo transcriptomes - TBroTeam/TBro
github.com
October 28, 2025 at 10:42 PM
There might be some good test cases in here, maybe this line? github.com/apollographq...
github.com
October 28, 2025 at 10:39 PM
So does mine with RegExp. If you need some edge case tests, I'm sure I can find you some 😅
October 28, 2025 at 8:05 PM
That was the link I was looking for.
I just quoted their plea for money and responded with something along the line "this is a private static HTML page. I'm sure you'll understand how ridiculous this sentence is".
I hope that's the last I hear of them :(
October 28, 2025 at 9:00 AM
Can't you configure a different pixel density per screen?
October 15, 2025 at 6:51 AM
Yeah, disabling TOTP is a mistake.
October 14, 2025 at 6:34 PM
Does it have an exports field in package.json, but that entry is missing in there?
October 14, 2025 at 5:06 PM
Isn't that only true if it's about a user-facing password?
Yeah, for tokens it's not really safer, but also doesn't seem less safe.
October 12, 2025 at 8:56 PM
I mean somehow these last few ones managed to be worse in quality than the AI slop PRs and that in itself is an achievement 🙄
October 12, 2025 at 8:52 PM