The list at the end isn't that good though. It's basically dictating this Matt Dugan's preferences. The third one about seven systems is both an exaggeration and a demand.
The rest of this page makes me think it would be really hard to work with Matt, and I'd probably just pass back when I was running projects. It's not worth the effort.
Other than the one about using only one platform, which you referenced, it seems like he's really just asking for clarity from maintainers about what contributions they would like, and how they would like them to be provided.
What items on the list do you think are just the author's preferences, but other potential contributors wouldn't like? It seems unlikely that contributors would prefer NOT to know if the maintainer doesn't want PRs, or would prefer NOT to have an example of how to contribute, e.g.
>The third one about seven systems is both an exaggeration and a demand.
I don't know how many times in the post they say some variation of "it's your stuff, do whatever you want", but it's certainly more than once. While they didn't explicitly say it (again) in this particular sentence, "do what you want" is repeated enough times throughout the page that it's pretty clear that nothing on this page is a "demand".
"You provide an amazing service and I want to help. But part of helping is I need to understand what is it that you would like me to do."
Is a pretty reasonable take. I don't know how that translates to "really hard to work with", but, in their own words: "It's your project, you are welcome to do with it whatever you want".
Nope. <h1 class="foo>bar">My First Heading</h1> will misparse. (This is valid HTML 5.) You really need recursive regex or something equivalent in power, otherwise you will always fail.
We use it on slack and irc for debugging people's regular expressions all the time. Being able to have 30 revisions to a base regex to troubleshoot is fantastic.
I guess I don't understand. Mind throwing up an example with multiple test strings on regex101.com ? I'd like to take a look and see if I can make a regex which does what you want.
So if you could write the examples there, and then a description like you would tell your mom of what you want I'll see what I can do.
Honestly don't let this get you down, here's a learning plan (use regex101 to learn)
1) Learn PCRE regex.
2) Try regex golf or cross words to learn PCRE regex.
3) Take the quiz on regex101.
Once you're done with all 3:
Learn the minor/major differences in the other languages. There aren't many. For example this named capture group:
(?<somename>someregex)
Would look like this in a different language:
(?P<somename>someregex)
There's some differences about what language can and cannot do like recursion because someone thought it was a great idea to make javascript awful at regex, but that's besides the point. Regex is totally worth learning.
The rest of this page makes me think it would be really hard to work with Matt, and I'd probably just pass back when I was running projects. It's not worth the effort.