← Back to context

Comment by esafak

2 days ago

Could you upstream that change in order to make it an extension in the future? I think people would not value it any less.

We don't mind upstreaming. But I don't think Google Chrome/Chromium wants to expose it as an API chrome extensions, if not they would've done this long time ago.

From Google's perspective, extension are meant to be lightweight applications, with restricted access.

  • I'm not really interested in AI agents for my webbrowser, but it would be pretty cool to see a fork of chromium available that, aside from being de-googled, relaxes all the "restricted access" to make it more fun to modify and customize the way you guys are. Just a thought, may be more of a market for the framework more than the product :)

    See Sciter. A very cool, super lightweight alternative to Electron, but unfortunately it seems like a single developer project and I could never get any of the examples to run.

    https://sciter.com/

    • I always wonder about what sort of js engine such projects use since at the end of the day imo, it is all just a dance b/w js engine, html and css. Html & Css feels a little solved problem but the problem is of the js engine.

      Sciter uses quickjs and I just checked and its like 35-36x times slower than V8 JIT

      Also another interesting rabbit hole is that I found Duktape in the quickjs benchmarks and I saw https://blogcpp.org/ as one of the projects within Duktape but I can't even see the project on github. We really need some better way of preserving open source stuff I guess

      2 replies →

    • Yes, we want to do this too! We'll expose much more richer APIs.

      What use-cases do you have in mind? like scraping?