News for hackers. Stuff that matters.

A comment on Electron 7.0. Parent comment

Re:Electron 7.0 by judge2020 on Thursday October 24, 2019 @01:38PM (#21347047)
I imagine the different electron versions and different Chrome versions would make this hard without breaking things. Maybe a config option for "allow chromium between versions x and y" would solve this.
[ Parent | on HN ]
Re:Electron 7.0 by Hendrikto on Thursday October 24, 2019 @01:40PM (#21347071)
Shouldn‘t Chrome be backwards compatible? I would hope so at least.
[ Parent | on HN ]
Re:Electron 7.0 by judge2020 on Thursday October 24, 2019 @01:48PM (#21347182)
Most electron projects I've seen have used webpack targeting ES2017 or earlier anyways which makes this unlikely, but if you compile for ESnext (or don't compile at all) and use a new V8 feature, you wouldn't want Chrome 69 running your app and getting stuck on old V8 not being able to use the new feature.
[ Parent | on HN ]
Re:Electron 7.0 by pawelk on Thursday October 24, 2019 @05:22PM (#21349319)
Maybe it should, but it's not always the case. As a front end dev I have to fix issues related to bugs introduced by browser uptades every now and then and usually it's Chrome. On the web it's easy, deploy a fix and it's live. With a desktop app I can't even imagine the logistics involved.
[ Parent | on HN ]