no the fuck it's not. regex people live in another world

@NecroTechno I regret to admit I understood it, but I didn't know about the hyphen. Is there still time to save me, or am I too far gone?

@NecroTechno i got the intended behavior, but the bug wasn’t obvious to me

@NecroTechno ok i understood what the regex *does* but the intent is ambiguous. did the author want to match hyphens or every ascii character between , and . ?

@bri_seven it's actually from a blog post explaining how it works even though it looks like it shouldn't:

But as someone who only begrudgingly interacts with regex and stumbles through using it when I have to instead of just learning the syntax, I was amused by someone referring to the arcane syntax of regex as "clear enough".

@NecroTechno maybe i am just a weirdo but regex only looks hard. I only had to remember like 5-7 things to basically master it. it’s not like needing to memorise 5000 kanji to effectively read and write japanese .

@NecroTechno okay i have read the blog post, and i definitely would have looked up the ascii table if i weren’t lying in bed

@bri_seven @NecroTechno I would say it *is* hard in the sense that the terse and context-dependent* syntax leads to overlooked major bugs.

* ^ can mean “beginning of” or “not”, e.g.

@chucker @bri_seven @NecroTechno I think that's not a great example. In traditional regexp the only time a character is used differently is inside a group.

That said, perl regexp can be annoying with all the different variations of (?char.

Sign in to participate in the conversation

We are an instance for artists, queers, and technologists.