Tim Bray

The patterns are based on those of AWS EventBridge: https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-event-patterns.html - still lots of stuff there that Quamina doesn't have yet. The design can't get too open-ended because for Quamina...

That's the idea. Everything so far in Quamina is EB-compatible, with the exception of the * "shellstyle" pattern, and my belief is that EB would like to have that. There...

Thanks for that. There are a lot of things I could choose to work on, and input of the form “X would be useful to us” is helpful in prioritizing.

Possibly. But Jeff is a really smart guy. Steve Yegge blogged that the Amazon dogma that all software must be implemented as a callable service came from Jeff. Also, an...

I agree. Feel like proposing some language?

Doing this split would involve a bunch of weird corner cases. My intuition is that Alexa would stay on the Amazon side. But it'd be an interesting discussion.

First of all, I believe it's not just a Go thing, more or less every regex library has finite automata inside, isn't that the only sane approach? RE2::Set at one...

Right, and of course having backtracking doesn't mean you're not using DFAs. Sometime I will share the funny/horrible story about how the Java regex implementation blew up JRuby on Rails....

Doesn't sound crazy. Empirically, the groups using Quamina's big sister inside AWS seemed to like the pattern language, basically 100% of our complaints were about wanting new matching features and...

Hmm. At runtime, nothing exists but the compiled DFA structure starting at the coreMatcher type. The current pattern language and a hypothetical SQL-like expression are probably about equally removed from...