Skip to content

Commit

Permalink
docs(all): updated readme
Browse files Browse the repository at this point in the history
  • Loading branch information
KFlash authored Feb 15, 2020
1 parent 162be26 commit 1c39252
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,10 +62,10 @@ This is the available options:

## What is Seafox?

This is my private parser code made public. It strictly conforms to the standard ECMAScript® 2020 (ECMA-262 10th Edition) language specification, and can not be used as an drop-in replacement for other parsers.
This is my private parser code made public. It strictly conforms to the standard ECMAScript® 2020 (ECMA-262 10th Edition) language specification, and can not be used as an drop-in replacement for other parsers, because they are using a `parse()` method as an common public API to parse javascript code.

The main reason for this is that all parsers uses a `parse()` method - Seafox uses either [`parseScript`](https://tc39.github.io/ecma262/#sec-parse-script) or [`parseModule`](https://tc39.github.io/ecma262/#sec-parsemodule).
Seafox uses either [`parseScript`](https://tc39.github.io/ecma262/#sec-parse-script) or [`parseModule`](https://tc39.github.io/ecma262/#sec-parsemodule).

`Seafox` main focus is performance, and if you are soft hearted and / or can't understand super low level code - this parser isn't for you :)
The main focus for `Seafox` is performance, and if you are soft hearted and / or can't understand super low level code - this parser isn't for you :)

I would recommend to use the [`Meriyah parser`](https://github.com/meriyah/meriyah/) instead of `Seafox` if you need a parser that behave like other public parsers, and also if you are in need of performance even the fact that Seafox is 15 - 25 % faster than the mentioned parser.

0 comments on commit 1c39252

Please sign in to comment.