I really hope they consider that Linux' graphic stack isn't an end in itself, but a driver for running the relative wealth of graphic apps (GIMP, Inkscape, Krita, Blender, Firefox, and more) many people spent the last 30 years or so developing. Those aren't going to be rewritten from scratch into Electron-based apps or whatever, and loosing them, as well as BSD and Mac OS compat, is no option IMHO.
Why do you think those apps would need to be rewritten and what has electron to do with that? Most of these apps already run natively on top of Wayland, as they are written using a toolkit like GTK or QT and those toolkits support Wayland.
Also, there is XWayland, which implements the X protocol on top of Wayland, so any X application should continue to run. The only thing they talked about stopping development on is the standalone X server X.org.
I have been using Wayland on my desktop for a while and am quite happy about it.
Electron needs to be pushed down the stack to the bare metal, to become the window system itself. Then there will only be one instance of it running, that every other application can share, and the window manager and user interface and networking can all use standard web technologies, that everything else uses.
If you disagree, then tell me what X-Windows or Wayland can do that a modern web browser with bare metal drivers couldn't do much better?
You've got JavaScript and WebAssembly for programming, WebGL and and and DHTML and CSS for drawing (including low latency rendering with desynchronized canvases), JSON and XML and ArrayBuffer for data representation, HTTP and WebSockets and WebRTC for networking. What is it missing?
https://developers.google.com/web/updates/2019/05/desynchron...
There's really no need for X-Windows or Wayland any more.
I have a project that involves a compiler written in Prolog targeting Prof. Wirth's RISC chip (for Project Oberon[1]), and I want to make it easily accessible.
I can use e.g. TCL/Tk/Tkinter/Python+SWI-Prolog, and make a native app that the user has to install... or...
There is a Prolog in JS[2], and an emulator for the chip in JS[3], and rich widget frameworks (I like Knockout[4], but there are literally dozens in JS), so it's pretty easy to make a SPA that shows off the code (literate programming style) along with live compilation and emulation, and you can even let users save their work[5]. "Installation" is just visiting the page.
I keep trying to come up with reasons NOT to go that route (out of some perhaps-misplaced JS prejudice) and I can't.
> There's really no need for X-Windows or Wayland any more.
Indeed!
[1] http://www.projectoberon.com/
[2] Tau Prolog http://tau-prolog.org/
[3] http://schierlm.github.io/OberonEmulator/ https://github.com/schierlm/OberonEmulator