I completely agree with the email one, that's also the one I went with in most of my projects. I convinced some teachers in the past that Regex is not the best tool for email validation and that we should use that pattern in frontend instead.
Also I figured you didn't actually hate the thing if you created a whole website about the thing 😂😝.
You've done a good job of explaining it, although some patterns (such as the IP one) could probably be simplified a bit.
I'll definitely forward your website if I see someone struggling. Great job!
Thank you. I need to improve the explanations as well. (Will fix those :) )
at some point, I really felt embarrassed to share this.
It's been sitting in my Github for a while and I finally decided to share and see what everyone else thinks about it.
Your feedback has been of great help :D (there is also a beginners tutorial article in the making)
Basically, since there are so many rules and edge cases about emails, creating a Regex to solve that problem is not a productive approach since if new edge cases are created or found, maintenance instantly becomes hell and the pattern most likely has to be recreated from scratch.
Fortunately, people have already poured tons of hours into solving that problem for us and we can build on their shoulders.
Another example where regex looks like an appropriate tool but isn't is with parsing HTML. It sprung a famous Stack overflow question answer.
I completely agree with the email one, that's also the one I went with in most of my projects. I convinced some teachers in the past that Regex is not the best tool for email validation and that we should use that pattern in frontend instead.
Also I figured you didn't actually hate the thing if you created a whole website about the thing 😂😝.
You've done a good job of explaining it, although some patterns (such as the IP one) could probably be simplified a bit.
I'll definitely forward your website if I see someone struggling. Great job!
Thank you. I need to improve the explanations as well. (Will fix those :) )
at some point, I really felt embarrassed to share this.
It's been sitting in my Github for a while and I finally decided to share and see what everyone else thinks about it.
Your feedback has been of great help :D (there is also a beginners tutorial article in the making)
If your repo is public, I'd be glad to help with a PR or two! 😊
Here you go 😊:
github.com/geongeorge/i-hate-regex
The code is not the most elegant (I have to warn you)
Huh. I always do complex stuff like this with regex, in frontend as well as in backend.
What would be your tool of choice?
Depends on the language, in PHP for example, there's this library: github.com/egulias/EmailValidator
Basically, since there are so many rules and edge cases about emails, creating a Regex to solve that problem is not a productive approach since if new edge cases are created or found, maintenance instantly becomes hell and the pattern most likely has to be recreated from scratch.
Fortunately, people have already poured tons of hours into solving that problem for us and we can build on their shoulders.
Another example where regex looks like an appropriate tool but isn't is with parsing HTML. It sprung a famous Stack overflow question answer.
I just launched iHateRegex on Producthunt 😺
👉👉
producthunt.com/posts/i-hate-regex