4 ms·

From a user perspective (i.e., not a developer one), what have either of these projects improved since the old days of GTK2 and X11? Maybe I'm not enough of a

From a user perspective (i.e., not a developer one), what have either of these projects improved since the old days of GTK2 and X11? Maybe I'm not enough of a power user, but I see no tricks in my Linux GUI today that weren't already there 15 years ago. Preemptively, I reject the "security" answer, since Intel/ AMD/NSA/Mossad can already peek my RAM at will. The whole mess feels like corporate sabotage.

yakubin 3y ago
In the beginning of Gnome 3 I loved this feature where you could reply to someone’s chat messages straight from the notification without switching apps/windows: <https://lh6.googleusercontent.com/-hIyeIWfFyvc/ToRSxqZnFQI/AAAAAAAAGEM/yXi5buduS4w/s2000/chat-reply.png https://lh6.googleusercontent.com/-hIyeIWfFyvc/ToRSxqZnFQI/A...>. It eliminated a costly mental context switch. But XMPP is dead, so I don’t use such apps anymore. I also haven’t been using Gnome for a very long time now. I’ve read somewhere that they removed this feature though.
- deleted 3y ago
  [deleted]
- MattJ100 3y ago
  XMPP isn't dead, but quite active: https://xmpp.org/blog/ https://xmpp.org/blog/ It's very possible your social circle is not on XMPP though. There's some light at the end of the tunnel with the EU's Digital Markets Act forcing the large messaging providers to provide interoperability - at a minimum this should enable better bridges between XMPP-based and proprietary systems. The active GTK clients these days are Dino and Gajim. Pidgin is still around, but has fallen very far behind with regards to features (they're in the middle of a rewrite that will hopefully address this).
kaba0 3y ago
Peeking at RAM and literally being able to record your whole screen from an npm package are two quite different levels of threats. Also, multi-monitor setups with different DPIs are not possible on X.
- hello_computer 3y ago
  Someone who has a malicious npm package running on his machine has bigger problems. It will already be able to read/write every file that the user can. Why is the screen so special that we need to break everything? I see so many screencast/input-sharing/macro apps on github that have been in a holding pattern--for years!--waiting on wayland to either fix a bug or add a feature. 14 years of wayland so far, and we still can't do things that every other major OS's display server handles easily. At this rate, wayland will certainly become exploit-free, since no one will be using it.

yakubin 3y ago

In the beginning of Gnome 3 I loved this feature where you could reply to someone’s chat messages straight from the notification without switching apps/windows: <https://lh6.googleusercontent.com/-hIyeIWfFyvc/ToRSxqZnFQI/AAAAAAAAGEM/yXi5buduS4w/s2000/chat-reply.png https://lh6.googleusercontent.com/-hIyeIWfFyvc/ToRSxqZnFQI/A...>. It eliminated a costly mental context switch. But XMPP is dead, so I don’t use such apps anymore. I also haven’t been using Gnome for a very long time now. I’ve read somewhere that they removed this feature though.

deleted 3y ago
[deleted]
MattJ100 3y ago
XMPP isn't dead, but quite active: https://xmpp.org/blog/ https://xmpp.org/blog/ It's very possible your social circle is not on XMPP though. There's some light at the end of the tunnel with the EU's Digital Markets Act forcing the large messaging providers to provide interoperability - at a minimum this should enable better bridges between XMPP-based and proprietary systems. The active GTK clients these days are Dino and Gajim. Pidgin is still around, but has fallen very far behind with regards to features (they're in the middle of a rewrite that will hopefully address this).

kaba0 3y ago

Peeking at RAM and literally being able to record your whole screen from an npm package are two quite different levels of threats. Also, multi-monitor setups with different DPIs are not possible on X.

hello_computer 3y ago
Someone who has a malicious npm package running on his machine has bigger problems. It will already be able to read/write every file that the user can. Why is the screen so special that we need to break everything? I see so many screencast/input-sharing/macro apps on github that have been in a holding pattern--for years!--waiting on wayland to either fix a bug or add a feature. 14 years of wayland so far, and we still can't do things that every other major OS's display server handles easily. At this rate, wayland will certainly become exploit-free, since no one will be using it.