Mozilla had an alternative to Electron and they dropped it before Electron was born even. Who do we have to blame if not them? Their priorities have always been wrong.

Any developers using it, yes that also includes the likes of VSCode.

The priorities of anyone that uses Electron are the ones that are wrong, picking developer comfort instead of what is good for users or the Web.

Use a daemon with local browser or the OS webwidgets.

Yes it is more work that coding against Chrome APIs, but that is the whole point if one cares about the Web in general, otherwise those developers could just update their CVs to ChromeOS developer.

That doesn't make any sense. Using an electron app isn't the same as someone accessing web sites with chrome.

Sure it does, using Electron is picking the easy way of coding against Chrome specific APIs, instead of what Web is capable of across all browsers.

What you're saying is not wrong, but that's only about developers. Users have no say in the stack used in an app, so using that app in today's landscape of walled Gardens makes no difference in terms of chrome's dominance.

That app only exists because those developers decided to support Google's agenda.

Programs built on electron are using chrome is an isolated way, they aren't skewing the percentage of people who access web sites with chrome.

They are increasing the amount of Chrome deployments and developers using Chrome only APIs.

Is there an alternative to Electron that uses Gecko instead of Blink/WebKit?

Yes, the right way to do it, PWAs or OS Web widgets.