110
OpenAI's Codex app has 70% GPU usage while it is “thinking” due to tiny useless animation (github.com)
submitted 3 months ago* by to c/programmerhumor@lemmy.ml
20 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 7 points 3 months ago (3 children)

Isn't the whole point of regex to toil for 3 hours to write something very specific you will only ever use once?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 7 points 3 months ago* (2 children)

    Isn't the whole point of regex to toil for 3 hours to write something very specific you will only ever use once?

    /((?!([es]))y)(?:.*?)((?!(s))e)(?:.*?)(s)/

    Tap for spoilerIt's a Regex that checks if the letters for the word "yes" exists within a text in order. I call it the yesnometer

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 3 months ago (1 child)

    What's wrong with y.*e.*s ?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 6 points 3 months ago

    Nothing is wrong with that, but it will give you different output. I tend to like using capture groups just out of habit, it makes it more flexible and useful in future. Most of my co-workers hated Regex so I tried to make it easy for them.

    I also wanted the letters to be as close together as possible. In this example it doesn't matter, but in other texts it might. Yours will find the first y, then the furthest possible e, then the furthest possible s. So you might get output where there's a y on line 1 and the e s at the very end of the text. Nothing wrong with that, it's just not what I was envisioning.

    Also it's funnier in this context to have a complicated regex.

  • permalink
  • fedilink
  • source
  • parent