-
Notifications
You must be signed in to change notification settings - Fork 6
Difference between the original ometa-js #8
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
Comments
@CMCDragonkai take a loot at my fork https://github.com/veged/ometa-js — we rewrite it couple of times for better performance |
Hey, I didn't actually see this when it was first posted, sorry! Anyway, the main selling point of this fork is the ability to use the OMeta grammar to enable CodeMirror highlighting/autocomplete functionality. It is used on http://www.sbvr.co/ to enable the highlighting and the autocomplete (ctrl+space), an example of the SBVR language (to see the highlighting in action) can be found at http://www.sbvr.co/#/lPWulm |
Could you give a summary of differences between: Veged's fork, Page's fork, and metacoffee(https://github.com/xixixao/meta-coffee) @veged You mentioned performance, so are you saying it's faster than @Page- 's fork? |
I doesn't compare it to @Page- one, but it's for sure faster than original |
@veged Do you have any benchmarks? How did you make it faster? |
we use it a lot in various tools inside Yandex and main benchmark is real life usage — maybe @indutny (as main author) has some synthetics benchmarks also we just rewrite it from scratch couple of times keeping performance in mind |
Hey I noticed that ometa-js has been somewhat abandoned, and you've added a lot of work to this fork. Would you be willing to summarise the differences between the original one and your one?
The text was updated successfully, but these errors were encountered: