tobiu

51 ms·

181.
by tobiu 7y ago
it definitely is the bottleneck, which is the reason we should move all other possible tasks out of main. in this (neo.mjs) case main applies the deltas, forwards dom events to the app worker & serves as a message bus as long as workers
182.
by tobiu 7y ago
scroll down on the example page please: the dist/development & dist/production versions do work in other browsers and do not need a flag.
183.
by tobiu 7y ago
Let me shed some light into this: Chrome 80 will most likely get released in January, since Chrome Canary already no longer needs the flag. You can run the dist/development and dist/production versions of neo inside FF & Safar
184.
by tobiu 7y ago
This sounds like a philosophical question :) In general humans are afraid of radical new ideas (at least most). There is also the "riding the wave" phenomenon, which is slowing down innovations to some degree. Meetups or conferenc
185.
by tobiu 7y ago
there 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&#x2
186.
by tobiu 7y ago
at 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 (
187.
by tobiu 7y ago
in case it does cause problems, it would be very easy to change the file names. the dist versions do use .js files, since webpack compiled modules are not real ones. feel free to open a ticket inside the issues tracker with more input about
188.
by tobiu 7y ago
It is not used in production yet (the repo just went online on Nov. 23rd). This will change soon though. I am not officially allowed to talk about it yet, but if you look at my linked in profile, you might get an idea. The motivation part w
189.
by tobiu 7y ago
To be honest, I have not looked at this project yet. In neo.mjs, there is an app worker which contains most parts of the framework and your apps (can be more than 1). The vdom comparison happens inside the vdom worker (which mostly makes se
190.
by tobiu 7y ago
Important: at this point the examples are intended for desktop browsers. Mobile support is on my todo list, but will take some time.
191.
by tobiu 7y ago
please see the comment below: "Important: at this point the examples are intended for desktop browsers. Mobile support is on my todo list, but will take some time."
192.
by tobiu 7y ago
You mean the file name extension .mjs? If so: https://medium.com/passpill-project/files-with-mjs-extension... It got popular in nodejs first to name files containing JS modules .mjs, but it starting to get a standard i
193.
by tobiu 7y ago
Important: at this point the examples are intended for desktop browsers. Mobile support is on my todo list, but will take some time.
194.
by tobiu 7y ago
Actually there is a link to the online examples at the top of the readme: 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 fu
195.
Show HN: Neo.mjs – the webworkers driven UI framework(neomjs.github.io)
3 points by tobiu 7y ago|1 comments
196.
Neo.mjs – Webworker-driven UI framework(github.com)
50 points by tobiu 7y ago|54 comments