Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

30$: Benchmark CLI throughput #240

Open
strager opened this issue Apr 23, 2021 · 1 comment
Open

30$: Benchmark CLI throughput #240

strager opened this issue Apr 23, 2021 · 1 comment
Labels
for hire Get paid for working on this task: https://quick-lint-js.com/hiring.html performance Slowness or potential optimization

Comments

@strager
Copy link
Collaborator

strager commented Apr 23, 2021

Compare performance of quick-lint-js' CLI against the following tools (in parse-only mode ideally):

  • ESLint
  • RSLint
  • deno lint
  • TypeScript
  • Flow
  • Acorn parser with Node.js
  • swc parser
  • Ratel parser
  • V8 parser
  • SpiderMonkey parser
  • QuickJS
  • Moddable XS
@strager strager added the for hire Get paid for working on this task: https://quick-lint-js.com/hiring.html label Apr 23, 2021
@strager
Copy link
Collaborator Author

strager commented May 1, 2021

This task might be done in Haskell (since that's what our LSP benchmarks are written in), but I'm open to different frameworks.

@strager strager added the performance Slowness or potential optimization label Dec 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for hire Get paid for working on this task: https://quick-lint-js.com/hiring.html performance Slowness or potential optimization
Projects
None yet
Development

No branches or pull requests

1 participant