rosie VS instaparse

Compare rosie vs instaparse and see what are their differences.

Our great sponsors
  • SonarLint - Clean code begins in your IDE with SonarLint
  • Mergify - Updating dependencies is time-consuming.
  • InfluxDB - Collect and Analyze Billions of Data Points in Real Time
rosie instaparse
4 7
- 2,664
- -
- 0.0
- 4 months ago
- Eclipse Public License 1.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of rosie. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-07-10.


Posts with mentions or reviews of instaparse. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-07-08.
  • Chumsky, a Rust parser-combinator library with error recovery
    8 projects | | 8 Jul 2022
    Caveats: I've used nom in anger, chumsky hardly at all, and tree-sitter only for prototyping. I'm using it for parsing a DSL, essentially a small programming language.

    The essential difference between nom/chomsky and tree-sitter is that the former are libraries for constructing parsers out of smaller parsers, whereas tree-sitter takes a grammar specification and produces a parser. This may seem small at first, but is a massive difference in practice.

    As far as ergonomics go, that's a rather subjective question. On the surface, the parser combinator libraries seem easier to use. They integrate well with the the host language, so you can stay in the same environment. But this comes with a caveat: parser combinators are a functional programming pattern, and Rust is only kind of a functional language, if you treat it juuuuust right. This will make itself known when your program isn't quite right; I've seen type errors that take up an entire terminal window or more. It's also very difficult to decompose a parser into functions. In the best case, you need to write your functions to be generic over type constraints that are subtle and hard to write. (again, if you get this wrong, the errors are overwhelming) I often give up and just copy the code. I have at times believed that some of these types are impossible to write down in a program (and can only exist in the type inferencer), but I don't know if that's actually true.

    deep breath

    Tree-sitter's user interface is rather different. You write your grammar in a javascript internal dsl, which gets run and produces a json file, and then a code generator reads that and produces C source code (I think the codegen is now written in rust). This is a much more roundabout way of getting to a parser, but it's worth it because: (1) tree-sitter was designed for parsing programming languages while nom very clearly was not, and (2) the parsers it generates are REALLY GOOD. Tree-sitter knows operator precedence, where nom cannot do this natively (there's a PR open for the next version: Tree-sitter's parsing algorithm (GLR) is tolerant to recursion patterns that will send a parser combinator library off into the weeds, unless it uses special transformations to accommodate them.

    It might sound like I'm shitting on nom here, but that's not the goal. It's a fantastic piece of work, and I've gotten a lot of value from it. But it's not for parsing programming languages. Reach for nom when you want to parse a binary file or protocol.

    As for chumsky: the fact that it's a parser combinator library in Rust means that it's going to be subject to a lot of the same issues as nom, fundamentally. That's why I'm targeting tree-sitter next.

    There's no reason tree-sitter grammars couldn't be written in an internal DSL, perhaps in parser-combinator style ( does this). That could smooth over a lot of the rough edges.

  • Langdev in Clojure
    2 projects | /r/Clojure | 28 Jun 2022
    Sure, you can use to create parser for any language you want, or simply create DSL in basic clojure types, like vectors.
  • Formal Specification and Programmatic Parser for Org-mode
    9 projects | /r/emacs | 10 Jan 2022
    Enter org-parser! It is indeed such a thing implemented already! Remember the magical parser I mentioned above? It is already implemented here Engelberg/instaparse too (in a Lisp)! org-parser is built on top of it by providing a formal specification for org-mode in the EBN form. Any proof that org-parser works? Indeed, there is the celebrated organice which is built on top of it. Kudos for 200ok-ch!
  • Casual Parsing in JavaScript
    5 projects | | 19 Aug 2021
    You might enjoy checking out Instaparse, a Clojure library. Its project page reads, “What if context-free grammars were as easy to use as regular expressions?”

    It’s not over-promising, either. I went from never having heard of it before to getting complete and correct parse trees of some ancient JSP Expression Language in about 20 minutes. Most of that time was spent typing in the BNF description that I could find only in an image.

  • Parsing Tools
    5 projects | /r/ProgrammingLanguages | 22 Apr 2021
    Instaparse sounds pretty close to what you're looking for assuming you're ok being limited to context-free grammars.

What are some alternatives?

When comparing rosie and instaparse you can also consider the following projects:

rakudo - 🦋 Rakudo – Raku on MoarVM, JVM, and JS

chumsky - Write expressive, high-performance parsers with ease.

parser-combinators - Parser combinators.

parser - Parser combinators

tree-sitter-org - Org grammar for tree-sitter

yieldparser - Parse using JavaScript generator functions — it’s like components but for parsing!

rust - Empowering everyone to build reliable and efficient software.

alass - "Automatic Language-Agnostic Subtitle Synchronization"


nom - Rust parser combinator framework

sci - Configurable Clojure/Script interpreter suitable for scripting and Clojure DSLs

org-parser - org-parser is a parser for the Org mode markup language for Emacs.