0.00 Regex is dead. We replaced it

Name: HRCB Evaluation: Regex is dead. We replaced it
Item: Regex is dead. We replaced it
Rating: 0
Author: Human Rights Observatory

Model: deepseek/deepseek-v3.2-20251201 0.00 @cf/meta/llama-4-scout-17b-16e-instruct lite 0.00 @cf/meta/llama-3.3-70b-instruct-fp8-fast lite 0.00 Compare

0.00	Regex is dead. We replaced it (matchlang.comS:ND)
	8 points by hollowsolve 4 days ago \| 9 comments on HN \| Neutral Landing Page · v3.7 · 2026-03-02 16:23:32 · from archive

Summary Technical Software Tool Neutral

The content is a minimal landing page for a programming tool called Match, which offers pattern matching to replace regex. No human rights themes are explicitly or implicitly addressed in the observable content. The evaluation finds no directional lean regarding human rights, resulting in neutral scores across all UDHR provisions.

Article Heatmap

Negative Neutral Positive No Data

Aggregates

Weighted Mean	0.00	Unweighted Mean	0.00
Max	0.00 N/A	Min	0.00 N/A
Signal	0	No Data	31
Volatility	0.00 (Low)
Negative	0	Channels	E: 0.6 S: 0.4
SETL ℹ	ND

Evidence 0% coverage ℹ

    31 ND 

Theme Radar

HN Discussion 4 top-level · 2 replies

hollowsolve 2026-02-26 17:17 UTC link

We built Match, a pattern matching language that compiles to WASM and replaces regex with readable grammars.

Instead of this: ^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}$

You write this:

email: username then "@" then domain

username: one or more of (letter, digit, ".", "_", "-")

domain: one or more of (letter, digit, "-") then "." then between 2 and 6 letters

Match features:

- WASM JIT + JS JIT: matches or beats native regex on most patterns

- Linear-time parsing, no backtracking, no ReDoS, ever

- Full parse trees with named extractions, not just match/no-match

- Zero dependencies, ~7KB, MIT licensed

- Composable grammars via modules

Website: https://matchlang.com

Performance: https://matchlang.com/docs/api/performance

GitHub: https://github.com/hollowsolve/Match

sgt 2026-02-26 17:19 UTC link

How about performance?

andOlga 2026-02-27 05:13 UTC link

Do you genuinely, truly believe that "4 digits then "-" then 2 digits then "-" then 2 digits" is more readable than "\d{4}-\d{2}-\d{2}"? Do you think your walls of text won't make everyone's eyes glaze over a few lines in? More importantly, do you believe it's more writable? A lot of regex operations are ad-hoc, and being able to type them out quickly and look at them in a small text field at a glance is very important. And as far as coding is concerned, well, your thing is useless outside of the JS ecosystem, is it not?

Dead? Replaced?... Your toy is cute, but it's more suited as a regex generator, or perhaps parser/"explainer" (but we already have several well-known projects there) than a standalone tool.

AkshatM 2026-02-27 05:59 UTC link

The effort here is laudable, and this is cool! But your real competition isn't regexes, but parser combinator libraries. For cases where readability and matching matter, parser combinators are the go to. It's a bit difficult to see how this improves on that front.

hollowsolve 2026-02-26 17:22 UTC link

Performance breakdown: https://matchlang.com/docs/api/benchmarks

gus_massa 2026-02-27 17:49 UTC link

The preferred style here for the titles is more dry, something like "Matchlang: A pattern matching language that replaces regular expressions. Full parse trees, no ReDoS" or a shorter version like "Matchlang: A replacement for regular expressions. Full parse trees, no ReDoS".

If you write in the title "Regex is dead" people will get skeptical and ask for proofs.

Editorial Channel

What the content says

Preamble Preamble