#parsing — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #parsing, aggregated by home.social.
-
Parse, Don’t Validate—in a Language That Doesn’t Want You To, by (not on Mastodon or Bluesky):
https://cekrem.github.io/posts/parse-dont-validate-typescript/
-
The fastest way to match characters on ARM processors?, https://lemire.me/blog/2026/04/19/the-fastest-way-to-match-characters-on-arm-processors/.
In this article, Lemir talks about two SIMD ARM SVE/SVE2 instructions: `match` and `nmatch`, which fit nicely in the _vectorized classification_ step of `simdjson`. These instructions improve the performance of `simdjson` from 11.4Gb/s to 14.4Gb/s.
-
The fastest way to match characters on ARM processors?, https://lemire.me/blog/2026/04/19/the-fastest-way-to-match-characters-on-arm-processors/.
In this article, Lemir talks about two SIMD ARM SVE/SVE2 instructions: `match` and `nmatch`, which fit nicely in the _vectorized classification_ step of `simdjson`. These instructions improve the performance of `simdjson` from 11.4Gb/s to 14.4Gb/s.
-
The fastest way to match characters on ARM processors?, https://lemire.me/blog/2026/04/19/the-fastest-way-to-match-characters-on-arm-processors/.
In this article, Lemir talks about two SIMD ARM SVE/SVE2 instructions: `match` and `nmatch`, which fit nicely in the _vectorized classification_ step of `simdjson`. These instructions improve the performance of `simdjson` from 11.4Gb/s to 14.4Gb/s.
-
The fastest way to match characters on ARM processors?, https://lemire.me/blog/2026/04/19/the-fastest-way-to-match-characters-on-arm-processors/.
In this article, Lemir talks about two SIMD ARM SVE/SVE2 instructions: `match` and `nmatch`, which fit nicely in the _vectorized classification_ step of `simdjson`. These instructions improve the performance of `simdjson` from 11.4Gb/s to 14.4Gb/s.
-
The fastest way to match characters on ARM processors?, https://lemire.me/blog/2026/04/19/the-fastest-way-to-match-characters-on-arm-processors/.
In this article, Lemir talks about two SIMD ARM SVE/SVE2 instructions: `match` and `nmatch`, which fit nicely in the _vectorized classification_ step of `simdjson`. These instructions improve the performance of `simdjson` from 11.4Gb/s to 14.4Gb/s.
-
I do not see why a recursive-descent parser cannot have numeric precedences like a Pratt parser. You just move the order of productions freely, and let any production call any other.
Am I missing something?
-
Rewriting Our Rust Wasm Parser in TypeScript, by (not on Mastodon or Bluesky):
-
Rewriting Our Rust Wasm Parser in TypeScript, by (not on Mastodon or Bluesky):
-
Rewriting Our Rust Wasm Parser in TypeScript, by (not on Mastodon or Bluesky):
-
Rewriting Our Rust Wasm Parser in TypeScript, by (not on Mastodon or Bluesky):
-
Rewriting Our Rust Wasm Parser in TypeScript, by (not on Mastodon or Bluesky):
-
🚀 Ohm's #PEG-to-WASM Compiler: because everyone needs a #parsing #tool that's 50x #faster to parse things nobody asked for! 😂 Forget about improving your life—just make #parsing 0.02 seconds quicker. Is it a bird? Is it a plane? No, it's an #unnecessary #compiler update! 🙄
https://ohmjs.org/blog/2026/03/12/peg-to-wasm #update #speed #improvement #tool #coding #humor #HackerNews #ngated -
Nobody Gets Fired for Picking JSON, but Maybe They Should?
Nobody Gets Fired for Picking JSON, but Maybe They Should?By Miguel Young de la Sota
Nobody Gets Fired for Picking JSON, but Maybe They Should?
JSON is extremely popular but deeply flawed. This article discusses the details of JSON’s design, how it’s used (and misused), and how
https://monodes.com/predaelli/2026/03/29/nobody-gets-fired-for-picking-json-but-maybe-they-should/
#Javascript #formats #JSON #parsing -
Nobody Gets Fired for Picking JSON, but Maybe They Should?
Nobody Gets Fired for Picking JSON, but Maybe They Should?By Miguel Young de la Sota
Nobody Gets Fired for Picking JSON, but Maybe They Should?
JSON is extremely popular but deeply flawed. This article discusses the details of JSON’s design, how it’s used (and misused), and how
https://monodes.com/predaelli/2026/03/29/nobody-gets-fired-for-picking-json-but-maybe-they-should/
#Javascript #formats #JSON #parsing -
Nobody Gets Fired for Picking JSON, but Maybe They Should?
Nobody Gets Fired for Picking JSON, but Maybe They Should?By Miguel Young de la Sota
Nobody Gets Fired for Picking JSON, but Maybe They Should?
JSON is extremely popular but deeply flawed. This article discusses the details of JSON’s design, how it’s used (and misused), and how
https://monodes.com/predaelli/2026/03/29/nobody-gets-fired-for-picking-json-but-maybe-they-should/
#Javascript #formats #JSON #parsing -
Nobody Gets Fired for Picking JSON, but Maybe They Should?
Nobody Gets Fired for Picking JSON, but Maybe They Should?By Miguel Young de la Sota
Nobody Gets Fired for Picking JSON, but Maybe They Should?
JSON is extremely popular but deeply flawed. This article discusses the details of JSON’s design, how it’s used (and misused), and how
https://monodes.com/predaelli/2026/03/29/nobody-gets-fired-for-picking-json-but-maybe-they-should/
#Javascript #formats #JSON #parsing -
Nobody Gets Fired for Picking JSON, but Maybe They Should?
Nobody Gets Fired for Picking JSON, but Maybe They Should?By Miguel Young de la Sota
Nobody Gets Fired for Picking JSON, but Maybe They Should?
JSON is extremely popular but deeply flawed. This article discusses the details of JSON’s design, how it’s used (and misused), and how
https://monodes.com/predaelli/2026/03/29/nobody-gets-fired-for-picking-json-but-maybe-they-should/
#Javascript #formats #JSON #parsing -
A Faster Alternative to Jq
https://micahkepe.com/blog/jsongrep/
#HackerNews #A #Faster #Alternative #to #Jq #json #parsing #programming #speed #optimization
-
A Faster Alternative to Jq
https://micahkepe.com/blog/jsongrep/
#HackerNews #A #Faster #Alternative #to #Jq #json #parsing #programming #speed #optimization
-
A Faster Alternative to Jq
https://micahkepe.com/blog/jsongrep/
#HackerNews #A #Faster #Alternative #to #Jq #json #parsing #programming #speed #optimization
-
A Faster Alternative to Jq
https://micahkepe.com/blog/jsongrep/
#HackerNews #A #Faster #Alternative #to #Jq #json #parsing #programming #speed #optimization
-
A nice survey of #ProgrammingLanguages that allow you to omit semicolons:
“No Semicolons Needed”, Terts Diepraam (https://terts.dev/blog/no-semicolons-needed/).
Via HN: https://news.ycombinator.com/item?id=47470200
On Lobsters: https://lobste.rs/s/09wmcz/no_semicolons_needed
#Programming #PLDI #Parsing #Lexing #Syntax #Grammar #Compilers
-
A nice survey of #ProgrammingLanguages that allow you to omit semicolons:
“No Semicolons Needed”, Terts Diepraam (https://terts.dev/blog/no-semicolons-needed/).
Via HN: https://news.ycombinator.com/item?id=47470200
On Lobsters: https://lobste.rs/s/09wmcz/no_semicolons_needed
#Programming #PLDI #Parsing #Lexing #Syntax #Grammar #Compilers
-
A nice survey of #ProgrammingLanguages that allow you to omit semicolons:
“No Semicolons Needed”, Terts Diepraam (https://terts.dev/blog/no-semicolons-needed/).
Via HN: https://news.ycombinator.com/item?id=47470200
On Lobsters: https://lobste.rs/s/09wmcz/no_semicolons_needed
#Programming #PLDI #Parsing #Lexing #Syntax #Grammar #Compilers
-
A nice survey of #ProgrammingLanguages that allow you to omit semicolons:
“No Semicolons Needed”, Terts Diepraam (https://terts.dev/blog/no-semicolons-needed/).
Via HN: https://news.ycombinator.com/item?id=47470200
On Lobsters: https://lobste.rs/s/09wmcz/no_semicolons_needed
#Programming #PLDI #Parsing #Lexing #Syntax #Grammar #Compilers
-
Another excellent post 👌🏽 from Russ Cox 👇🏽🫡:
“Floating-Point Printing And Parsing Can Be Simple And Fast” (https://research.swtch.com/fp).
On HN: https://news.ycombinator.com/item?id=46685317
On Lobsters: https://lobste.rs/s/nbsclr/floating_point_printing_parsing_can_be
#Programming #Math #FloatingPoint #Numbers #PLDI #Parsing #Printing
-
Another excellent post 👌🏽 from Russ Cox 👇🏽🫡:
“Floating-Point Printing And Parsing Can Be Simple And Fast” (https://research.swtch.com/fp).
On HN: https://news.ycombinator.com/item?id=46685317
On Lobsters: https://lobste.rs/s/nbsclr/floating_point_printing_parsing_can_be
#Programming #Math #FloatingPoint #Numbers #PLDI #Parsing #Printing
-
Another excellent post 👌🏽 from Russ Cox 👇🏽🫡:
“Floating-Point Printing And Parsing Can Be Simple And Fast” (https://research.swtch.com/fp).
On HN: https://news.ycombinator.com/item?id=46685317
On Lobsters: https://lobste.rs/s/nbsclr/floating_point_printing_parsing_can_be
#Programming #Math #FloatingPoint #Numbers #PLDI #Parsing #Printing
-
Another excellent post 👌🏽 from Russ Cox 👇🏽🫡:
“Floating-Point Printing And Parsing Can Be Simple And Fast” (https://research.swtch.com/fp).
On HN: https://news.ycombinator.com/item?id=46685317
On Lobsters: https://lobste.rs/s/nbsclr/floating_point_printing_parsing_can_be
#Programming #Math #FloatingPoint #Numbers #PLDI #Parsing #Printing
-
A Percise Parser, by @remyporter.bsky.social:
-
“Explainer: Tree-sitter Vs. LSP”, Ashton Wiersdorf (https://lambdaland.org/posts/2026-01-21_tree-sitter_vs_lsp/).
Via HN: https://news.ycombinator.com/item?id=46719899
On Lobsters: https://lobste.rs/s/qhickw/explainer_tree_sitter_vs_lsp
#LSP #TreeSitter #LanguageServerProtocol #Editors #SyntaxHighlighting #Parsers #Parsing
-
“Explainer: Tree-sitter Vs. LSP”, Ashton Wiersdorf (https://lambdaland.org/posts/2026-01-21_tree-sitter_vs_lsp/).
Via HN: https://news.ycombinator.com/item?id=46719899
On Lobsters: https://lobste.rs/s/qhickw/explainer_tree_sitter_vs_lsp
#LSP #TreeSitter #LanguageServerProtocol #Editors #SyntaxHighlighting #Parsers #Parsing
-
“Explainer: Tree-sitter Vs. LSP”, Ashton Wiersdorf (https://lambdaland.org/posts/2026-01-21_tree-sitter_vs_lsp/).
Via HN: https://news.ycombinator.com/item?id=46719899
On Lobsters: https://lobste.rs/s/qhickw/explainer_tree_sitter_vs_lsp
#LSP #TreeSitter #LanguageServerProtocol #Editors #SyntaxHighlighting #Parsers #Parsing
-
“Explainer: Tree-sitter Vs. LSP”, Ashton Wiersdorf (https://lambdaland.org/posts/2026-01-21_tree-sitter_vs_lsp/).
Via HN: https://news.ycombinator.com/item?id=46719899
On Lobsters: https://lobste.rs/s/qhickw/explainer_tree_sitter_vs_lsp
#LSP #TreeSitter #LanguageServerProtocol #Editors #SyntaxHighlighting #Parsers #Parsing
-
-
Why #Lexing and #Parsing Should Be Separate
"Summary: Do the easy thing with the fast algorithm, and the hard thing with the slow algorithm. Lexing and parsing are different things."
https://github.com/oils-for-unix/oils/wiki/Why-Lexing-and-Parsing-Should-Be-Separate
-
I Ported JustHTML From Python to JavaScript With Codex CLI and GPT-5.2 in 4.5 Hours, by @simon:
