4
Tech Talk: How Electron went Wayland-native, and what it means for your apps (www.electronjs.org)
submitted 7 months ago by to c/electron@programming.dev
comment fedilink hide all child comments

no comments (yet)

sorted by: hot top controversial new old
there doesn't seem to be anything here
11 comments in c/linux@lemmy.ml view that post
[–] 6 points 7 months ago (1 child)

Do they imply Wayland forces apps to have CSDs? It is only GNOME that does it.

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
    • [–] 2 points 7 months ago (1 child)

    Hold up. Is this the Electron that is effectively just google chrome running web apps ? I thought this was undesirable, it being bloated and slow? I've noticed a few server apps starting to use Electron, which seems like a bad idea. What have I missed, and why is it so important?

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
  • [–] [S] 2 points 7 months ago

    It certainly has it's issues. Takes up quite a bit of space since each app tends ships its own copy of electron (though distros like Arch do try to make apps share a single Electron build). Apps may ship out of date versions that may have security vulnerabilities, though it's not always the end of the world since they tend not to access outside of their own domains. As for slowness and resource usages, it's bit of a tricky subject; an Electron app can be optimized, but will always use quite a bit of RAM.

    Though undeniably they have been beneficial for Linux if only because it allows some companies to support Linux without too much extra work.

  • permalink
  • fedilink
  • source
  • parent
    • [–] 0 points 7 months ago (5 children)

    now to wait out the years for old game launchers and wine to follow suit, and years more for proton to get it...

  • permalink
  • fedilink
  • source
  • hideshow 5 child comments
    •
  • [–] 7 points 7 months ago (4 children)

    wine already has it...

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 0 points 7 months ago (3 children)

    electron/cef apps doing cross process rendering can't display sooo

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 7 months ago (1 child)

    no clue what you're saying... works on every system I have

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 7 months ago

    Then you're either not using the native wayland driver, or you're running apps that don't use cross-process rendering. Try Ubisoft Connect or Jagex Launcher. Ubisoft Connect just displays a tiny window with nothing in it, but is probably supposed to show an error message, and Jagex launcher just shows a black screen, according to this comment.

    So unless you use a wine version patched to include the cross-process rendering code that was apparently already developed by Collabora (which I think is located here), you're not gonna get these apps to work.

  • permalink
  • fedilink
  • source
  • parent
    • [–] 0 points 7 months ago*

    Electron can go eat a burrito suck 23 balls and die pissed itself

  • permalink
  • fedilink
  • source
    •
    6 comments in c/linux@programming.dev view that post
    [–] 11 points 7 months ago

    I think whoever wrote this likes Evangelion lol

  • permalink
  • fedilink
  • source
    •
    [–] 5 points 7 months ago* (3 children)

    It''s neat to learn about CSD. That flat frameless window with a custom title bar look is what I dislike the most about electron applications. Hopefully those become less apparent with these new updates.

  • permalink
  • fedilink
  • source
  • hideshow 3 child comments
    •
  • [–] 8 points 7 months ago (2 children)

    This is a GNOME problem, not a Wayland problem. The article says "On X11, the window manager typically supplies a window’s title bar and frame decorations. But [...] on Wayland, all you get back from the compositor is a plain rectangle." which makes it sound like this is a Wayland problem, but this isn't true.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 7 months ago (1 child)

    Ah I think I might be misunderstanding then.

    For this:

    Many popular apps, including Visual Studio Code, Obsidian, and Discord, use frameless windows with custom title bars. Prior to Electron 41, frameless windows did not support CSD at all, so they looked like featureless rectangles on Wayland.

    Am I misinterpreting that Electron on Wayland now supporting CSD for frameless windows would make it possible for developers currently using them to better mimic the look of Qt or Gtk apps (with shadows and rounded corners, etc.)?

    I'm using KDE Plasma and Electron apps sometimes have that sharp-cornered, shadowless window vs the way Qt or Gtk apps are rendered. The most noticeable difference for me is the lack of outline, rounded corners, or shadow.

    But do correct me if I'm wrong since I don't know much about Electron development.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 5 points 7 months ago*

    Basically, on any sane window manager no matter if Wayland or X11, you'll get the same frame for all apps for free.

    From all the big desktops it's only GNOME that somehow decided server-side decorations weren't a good idea implement, and now all Wayland apps have to hand-roll a hacky workaround. The "flat frameless window" look was Electron's GNOME workaround. What the article is describing is a more elaborate GNOME workaround. On e.g. KDE, none of these problems existed in the first place.

  • permalink
  • fedilink
  • source
  • parent
    • [–] 2 points 7 months ago

    All good stuff, been waiting for this.

  • permalink
  • fedilink
  • source
    •