he is telling about phoenix, basically a better and more secure version of x11
however unlike wayland it is based off of x11 code
if this project ever releases then what would it mean for haiku? would the x11 compatability layer become the phoenix compatability layer or would both co-exist? or is this useless?
another tool named package forge is also mentioned. would it be like pkgsrc on haiku if it was implemented?
We don’t actually have a X11 compat layer, we have a compat layer for i think libX11. aslong as that is still used for apps it will not really affect haiku much
From what I read, Phoenix is a full rewrite in Zig and not aimed to be a full X11 replacement. At least for now it needs Wayland. Since it handles things a bit differently, it would mean globally more protocols to implement in compatibility layer.
Package Forge is tool to make portable image formats … portable. So, it is completely a different thing of Haiku packages.
Phoenix sounds to me like a good project: re-making X11 for the future. It seems to aligns quite well with Haiku’s “back to basics” approach. Using zig is pretty neat. For us armchair followers after a less technical overview, it has been covered in OSnews.
For the future of X11 I thiik I would rather look at Wayback: A Wayland replacement for the whole X11 server • The Register which is already adopted by Freedesktop. It implements the x11 prtocol on top of wayland, aiming to be as small and simple as possible. So you can run all your existing x11 setup (including window manager and desktop environment), but it uses the modern wayland codebase for acceleration and interfacing with the videocard.
I don’t see how yet another X11 replacement would be relevant to Haiku.
We have XLibe as libX11 replacement that directly binds to native APIs and avoids the usual X11-way of going through a client-server architecture.
It’s used for very few applications currently,but if there’s demand,I’m sure it can be extended with features that Phoenix adds,and that should be easier than porting a display server made for Unix-like OSes that work fundamentally different than Haiku does.
The package forge project isn’t relevant to Haiku either.
They build statically linked packages for Linux,probably trying to somehow solve dependency hell or at least trying to get stuff working universally on any distribution.
Haiku isn’t Linux,it’s neither ABI nor API compatible,so stuff from there won’t work on Haiku,simple as that.
It’s interesting, in an off-topic sort of way, to see what the current Linux civil war is all about.
Ahh, yes, the other Linux civil war. a.k.a. Package Format of the Month.
HPKG does it all for me, thank you very much. We do not need another packaging format.