2 ms·
Until wlroots is statically linked into xfce compositor... you know, if we could avoid the mess of the bazillion of x11 libs all over again...
by sylware 2y ago
Until wlroots is statically linked into xfce compositor... you know, if we could avoid the mess of the bazillion of x11 libs all over again...
- kelnos 2y agoNot sure what you mean. Hopefully I'll be basing it on a released version of wlroots (or at least a non-released version that that will be released by the time I'm ready), which will be dynamically linked just like everything else. And even if it isn't, and it's statically linked, so what? RAM is cheap and plentiful in most places these days, and if you're really upset about it you can build it yourself with --disable-wayland or whatever. Anyway, the negativity is quite unnecessary and tiresome.
- sylware 2y agoBecause putting everything in shared libs is what made the mess of the bazillion of x11 libs, even though x11 is a IPC protocol. If I am upset about something, it is wlroots does not manage properly its symbol namespaces with the C preprocessor, that to reduce to near 0 the possibility to have symbol collision while static linking. The great thing is finally xfce is going to have its wayland compositor. And there, there is not negativity, only positivity, because the real core of wayland is orders of magnitude simpler than x11 core, and wayland is getting its way on mobile, which means with vulkan3d, dude, the future looks bright, not grim, cheer up.