Live data from Hacker News

Regex Blaster

mdp.github.io

51–58 of 58 posts

Re: Regex Blaster

#51
Really fun. I just wish that stats were saved in localhost (like combat mode progress) and that esc instantly ended the round if you know you will lose.

Re: Regex Blaster

#52
post #45

Earlier quoted context omitted.

no considering free windows being light theme only, it should be a button, not a "system default"

… is that even legal to do for microsoft? Are there no requirements to adhere to certain standards? Would have thought that is part of it.

what would the requirement be? "thou must provide the full paid service to those who do not pay"?

Re: Regex Blaster

#53
post #9
post #4

Every vibe coded site is too dark and the text is too small.

They all have this rounded box design as well. I wonder where that came from, I don't think it was a predominant style before.

Recently asked Codex (GPT-5.2) to write a small single-page HTML frontend to debug some REST endpoints. As it was just a one-off tool, I put in no instructions about looks or styling at all. Lo and behold, the tool it wrote came with exactly that round-box style.

It seems to be the "default" style of some models for some reason.

Which makes me wonder if people already experimented with different style suggestions to get different results: "Make it look like an 1998 GeoCities page" / 2005 Facebook / Newgrounds / DeviantArt / HN / one of those Windows XP simulators with built-in window manager / etc

Re: Regex Blaster

#54
Cute. I had a crack at it but for me the fatal flaw is having to specifically delete the last regex before entering the next one, especially as the action gets tight. Each regex should go away once it's submitted, duh...

Re: Regex Blaster

#55
I played through the training level and it took me a minute to realize it's sub string/grep match. So in the first training level the pattern . matches everything when it feels like it should be .* to match all the characters of the enemies.

The UI looks great!

Re: Regex Blaster

#57
post #4

Every vibe coded site is too dark and the text is too small.

And all the text is grey-on-grey and basically unreadable. Not to even mention accessibility.

Automated accessibility testing needs to be in your loop, whether you are using an llm or not. Aria labels are easy to get right but they are also easy to forget.
Post reply on HN