• dactylotheca
    link
    fedilink
    English
    769 months ago

    Some people, when confronted with a problem, think “I know, I’ll use regular expressions.” Now they have two problems.

    • qaz
      link
      fedilink
      269 months ago

      Regex really isn’t that bad when using named capture groups.

      • dactylotheca
        link
        fedilink
        English
        179 months ago

        Oh yeah they definitely have uses, but there’s a real tendency for people to go a bit crazy with them. Complex regexen aren’t exactly readable, there’s all kinds of fun performance gotchas, there’s sometimes other tools/algorithms that are more suitable for the task, and sometimes people try to use them to eg. parse HTML because they don’t know that it is literally impossible to use regular expressions to parse languages that aren’t regular

          • dactylotheca
            link
            fedilink
            English
            7
            edit-2
            9 months ago

            Oh yeah, extensions which make them non-regular definitely can make it possible, but just because it’s now somewhat possible with some regex engines doesn’t mean it’s a good idea

        • @FooBarrington@lemmy.world
          link
          fedilink
          59 months ago

          I’ve once written a JS decompiler (de-bundler?) using ~150 regex for step-wise transformations. Worked surprisingly well!

        • @bleistift2@sopuli.xyz
          link
          fedilink
          English
          39 months ago

          it is literally impossible to use regular expressions to parse languages that aren’t regular

          It’s impossible to parse the whole syntax tree, but that doesn’t mean you can’t get the subset you’re interested in.

    • @MashedTech@lemmy.world
      link
      fedilink
      29 months ago

      I learned Regex once and now it just works. Only problem for me is using MacOS so the Regex flavors aren’t consistent. But once I sort that, it’s smooth sailing.