3 ms·
Actually there is a link to the online examples at the top of the readme: https://neomjs.github.io/pages/ https://neomjs.github.io/pages/ This is a new paradig
by tobiu 7y ago
Actually there is a link to the online examples at the top of the readme: https://neomjs.github.io/pages/ https://neomjs.github.io/pages/
This is a new paradigm: you can now include JS modules directly into workers inside the browser. This will be fully supported in Chrome 80 (already works in canary). The concept makes debugging extremely convenient, since you get the real code without source-maps and the multi-threading gives a relly nice performance.
I just donated 1.5 years of my full and unpaid working time to the open source community with this :)
- PudgePacket 7y agoIs there a particular feature that this requires to work? Using Firefox so wondering what version I might expect to be able to use this.
- tobiu 7y agoat this point, FF & Safari are falling behind, which is sad. The dist versions work there, but for the dev mode, they need to catch up. The biggest problem is, that FF & Safari do not support modules inside the worker scope at all (although it is inside the W3C specs for a very long time). On top of this, FF does not support dynamic imports (they recently changed the dynamic import detection from a parse time to a run time error => before this point even unreachable code broke it).
- spankalee 7y agoThere's no sample code, even on that page. It's difficult to see what this looks like.
- tobiu 7y agothere are some examples & example apps inside the repo. i think the best example app to understand the mechanics at this point is the docs app: https://github.com/neomjs/neo/tree/dev/docs/app/view https://github.com/neomjs/neo/tree/dev/docs/app/view (e.g. look into the MainContainer & the matching controller)