The Author Online Book Forums are Moving

The Author Online Book Forums will soon redirect to Manning's liveBook and liveVideo. All book forum content will migrate to liveBook's discussion forum and all video forum content will migrate to liveVideo. Log in to liveBook or liveVideo with your Manning credentials to join the discussion!

Thank you for your engagement in the AoF over the years! We look forward to offering you a more enhanced forum experience.

364988 (3) [Avatar] Offline
#1
I was planning to move some existing stand-alone apps to NW.js or Electron but see that Google are dropping support for Chromium. What impact will this have on future use of NW.js and Electron?
paulbjensen (39) [Avatar] Offline
#2
Hi,

Are you referring to Chrome apps? If so then as far as I know NW.js plans to continue support for Chrome apps. Below is a link to their blog post about the topic:

https://nwjs.io/blog/chrome-apps-support/

As for Electron, Electron doesn't support Chrome apps and has no plans to:

https://github.com/electron/electron/issues/1498

Chromium is the open source web browser version of Google Chrome. I haven't seen anything from them indicating that they plan to no longer support Chromium, only that they plan to no longer support Chrome apps.
364988 (3) [Avatar] Offline
#3
Impact of Chromium discontinuation (error on my part)
Thanks, I read the Chromium blog, saw the discontinuance statements about chrome frame and chrome apps, and misinterpreted them.

I was searching for information about how much of ES6 Chromium supported. Having come late in the day to porting from a highly structured language (where the vendor has tried to expand the framework to encompass so many platforms that basic features no longer work), it seems attractive to port to fully typed and modular js rather than incorporate all the tricks necessary in the past.

However, my first reading of the Chromium blog raised what seem to be false concerns.

Thanks for your helpful comments.