Monaco-editor: How to generate a tokenizer from a tmLanguage.json file
ATT
datou0412
>All comments
From the readme
Why doesn't the editor support TextMate grammars?
All the regular expressions in TM grammars are based on oniguruma, a regular expression library written in C.
The only way to interpret the grammars and get anywhere near original fidelity is to use the exact same regular expression library (with its custom syntax constructs).
In VSCode, our runtime is node.js and we can use a node native module that exposes the library to JavaScript.
In Monaco, we are constrained to a browser environment where we cannot do anything similar.
We have experimented with Emscripten to compile the C library to asm.js, but performance was very poor even in Firefox (10x slower) and extremely poor in Chrome (100x slower).
We can revisit this once WebAssembly gets traction in the major browsers, but we will still need to consider the browser matrix we support, i.e. if we support IE11 and only Edge will add WebAssembly support, what will the experience be in IE11, etc.
masad-frost
on 26 Feb 2019
Related issues
robclive
路
3Comments
inf9144
路
3Comments
PinkyJie
路
3Comments
Spongman
路
3Comments
poloten4uk
路
3Comments
Most helpful comment
From the readme
Why doesn't the editor support TextMate grammars?
All the regular expressions in TM grammars are based on oniguruma, a regular expression library written in C.
The only way to interpret the grammars and get anywhere near original fidelity is to use the exact same regular expression library (with its custom syntax constructs).
In VSCode, our runtime is node.js and we can use a node native module that exposes the library to JavaScript.
In Monaco, we are constrained to a browser environment where we cannot do anything similar.
We have experimented with Emscripten to compile the C library to asm.js, but performance was very poor even in Firefox (10x slower) and extremely poor in Chrome (100x slower).
We can revisit this once WebAssembly gets traction in the major browsers, but we will still need to consider the browser matrix we support, i.e. if we support IE11 and only Edge will add WebAssembly support, what will the experience be in IE11, etc.