Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Two things that made me switch to XFCE, JavaScript based extensions affecting performance, complete refusal to add back support for Windows shading (roll up).


That's why System76 is writting extensions in Rust and runs them in seperate processes.


Whatever compiled language, even with my C related rants, I am happier with C written XFCE extensions than the GNOME JavaScript ones.

The separate process is an interesting point, back in the day dynamically loading code into the host process was the way to go, due to hardware resources and how demanding would be to use UNIX IPC for everything.

Now a couple of years later, with the existing hardware resources, and the ongoing stability and security issues of loading code into process, turns out separate process is a good idea after all.


which extensions are js-based?

there's no gnome extension to do roll-up windows?


All of them, since they replaced the C API with the JavaScript based one in GNOME 3.0

"GNOME Shell and extensions are written in GJS, which is JavaScript bindings for GNOME Platform APIs. For an overview of how extensions fit into GNOME Shell and the platform, see the Architecture page."

https://gjs.guide/extensions/

Roll-up was never an extension on UNIX windows managers, having to install one is a joke on us.

As for the GNOME developers stance on that, https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1028

Meanwhile XFCE, KDE, Windowmaker, Afterstep, Enlightment.... do them just fine.


the shade issue seems to be an issue with wayland and whatnot as far i can tell..


That is why I wrote "Meanwhile XFCE, KDE, Windowmaker, Afterstep, Enlightment.... do them just fine. " to make the point the others handle it without excuses.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: