You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
since GraalVM can run Javascript and offers a Relativ Compatible API to v8 The Chromium Embedder Framework could get used as raw building block for Cross Platform Desktop Applications using the Blink Rendering Engine and GraalVM Isolates for Code Processing.
i talked about that in issue: #229 which was related because i am also experimenting with Android browsers and running Software via GraalVM there to be more precise.
- Using the GraalVM as v8 Replacement in a CEF Fork
- augument security problems and apis that are problematic when they get accessed from the Public web.
- Define and create a standard for diffrent language workers to expose the languages in a web frindly way.
- in general all the work that got done in tc39 and Chromium and Moz to make sure that the web can not access the local pc
Publish vertx-chromium (ES4X + Chromium Ozon Aura Window Manager) aka Chromitex
(Chromium running fully bound to the vertx eventloop) nio gets used as transport so we can even channel EPOLL Like justJS does up to 400% Compared to nodejs libuv loop. Chromium internal uses also libuv
some chomium code now even depends on node code we share it at last to link at it on build chromium / external / github.com / v8 / node /
Create a small api to expose Ozone Aura Wayland x11 Support and Positioning APIS
Create a small api to hook into the chromium Platform Manager (devtools protocol)
As Part of that Refactor puppeteer npm package maintained by Chromium Devtools Protocol team.
The text was updated successfully, but these errors were encountered:
The Idea
since GraalVM can run Javascript and offers a Relativ Compatible API to v8 The Chromium Embedder Framework could get used as raw building block for Cross Platform Desktop Applications using the Blink Rendering Engine and GraalVM Isolates for Code Processing.
i talked about that in issue: #229 which was related because i am also experimenting with Android browsers and running Software via GraalVM there to be more precise.
(Chromium running fully bound to the vertx eventloop) nio gets used as transport so we can even channel EPOLL Like justJS does up to 400% Compared to nodejs libuv loop. Chromium internal uses also libuv
some chomium code now even depends on node code we share it at last to link at it on build chromium / external / github.com / v8 / node /
The text was updated successfully, but these errors were encountered: