I understand that Wayland doesn't support Xlib function calls. What are the options for those of us who rely on C code which which uses Xlib for 2d graphics and event handling? If I have to switch to e.g. GTK, I'd not only have to rewrite all the Xlib calls, but all the code which depends on this, as Xlib and GTK do graphics ad events quite differently.
Wayland is growing up. and now we don't have a choice
51–60 of 134 posts
Re: Wayland is growing up. and now we don't have a choice
#52XLibre talk is banned here, we DO have a choice.
Can you elaborate more on discussions about XLibre being banned on here? Are accounts that mention it getting banned? Is there just mass downvoting by partisans with some kind of agenda? I get that X11 has security issues, but NVIDIA drivers and Wayland still seem to have no support now and no support planned for the future, so Wayland is a non-negotiable non-option for many (most?) Linux desktop users, including mys…
[flagged]
Re: Wayland is growing up. and now we don't have a choice
#53Earlier quoted context omitted.
What's XLibre? Are they taking Linux desktop accessibility more seriously?
XLibre is a fork of Xorg X11's codebase started by a developer who got kicked out of the Xorg project because he was making lots of changes that broke everything and had a hard time getting along with the other devs. Another dev blindly applied his MRs assuming he had tested stuff before submitting the request and they had to go back and revert a bunch of stuff. Broke nvidia compatibility, broke xrandr extension, and…
Googler, NSA'er, or Red Hatter?
Re: Wayland is growing up. and now we don't have a choice
#54Re: Wayland is growing up. and now we don't have a choice
#55> GNOME’s Wayland session is now stable and usable with Orca.
They did that via an out-of-band D-Bus protocol, rather than going full Wayland. I'm all for keeping D-Bus around for backwards-compatibility (lots of things use AT-SPI2, and I certainly don't want a repeat of the CORBA -> D-Bus migration), but Wayland's AT support should be first-class, not relegated to proprietary GNOME extensions.
Per Matt Campbell's article https://blogs.gnome.org/a11y/2024/06/18/update-on-newton-the..., this decision has something to with security:
> Assistive technologies or other accessibility clients currently connect to the compositor through a D-Bus protocol, defined in the Mutter repository linked above. By exposing this interface via D-Bus rather than Wayland, we make it easy to withhold this communication channel from sandboxed applications, which shouldn’t have this level of access.
Re: Wayland is growing up. and now we don't have a choice
#56I understand that Wayland doesn't support Xlib function calls. What are the options for those of us who rely on C code which which uses Xlib for 2d graphics and event handling? If I have to switch to e.g. GTK, I'd not only have to rewrite all the Xlib calls, but all the code which depends on this, as Xlib and GTK do graphics ad events quite differently.
XWayland is still supported, and afaik will be for some time. It's only standalone Xorg which isn't.
Re: Wayland is growing up. and now we don't have a choice
#57I understand that Wayland doesn't support Xlib function calls. What are the options for those of us who rely on C code which which uses Xlib for 2d graphics and event handling? If I have to switch to e.g. GTK, I'd not only have to rewrite all the Xlib calls, but all the code which depends on this, as Xlib and GTK do graphics ad events quite differently.
[deleted]
Re: Wayland is growing up. and now we don't have a choice
#58Earlier quoted context omitted.
You keep assuming that it's HN staff, but HN articles very often get flagged by regular users when they get political, and having seen some of the comments on one of the other articles, including some of yours, I'm not the slightest bit surprised they got flagged. If people want Xlibre to have a shot at HN at all, those are things to fix. Making unsubstantiated claims about HN staff is not going to change anything -…
No, a project or a project leader having haters (just this thread there are 3 distinct people jumping in with various insults or fake news on normal questions) should not be enough for something to get censored. What kind of 'Why are you hitting yourself?' logic is that? > You keep assuming that it's HN staff, It's HN staff, and I've already explained it. Read back.
It's quite possible that there are just people flagging things without commenting. I do this all the time if the discussion looks particularly stupid, unproductive, bad-tempered, pointless, and so on - or some combination thereof. (I haven't done it in this case, but only because I was silly enough to comment. This thread has been quite reasonably flagged, I'd say.)
This is part of the how this particular site works. If you don't like it, that's fine, but you will have to go elsewhere to avoid it. And even if it is indeed the admins working away behind the scenes, a committee of shadowy puppetmasters directing their every move, suppression of X11 forks just one probing toothed tendril of this multi-armed octopus - well, this place was never a democracy anyway.
Re: Wayland is growing up. and now we don't have a choice
#59I understand that Wayland doesn't support Xlib function calls. What are the options for those of us who rely on C code which which uses Xlib for 2d graphics and event handling? If I have to switch to e.g. GTK, I'd not only have to rewrite all the Xlib calls, but all the code which depends on this, as Xlib and GTK do graphics ad events quite differently.
Isn't libwayland-client the replacement?
E.g. you now use the wayland calls instead of x11 calls
Re: Wayland is growing up. and now we don't have a choice
#60Earlier quoted context omitted.
No, a project or a project leader having haters (just this thread there are 3 distinct people jumping in with various insults or fake news on normal questions) should not be enough for something to get censored. What kind of 'Why are you hitting yourself?' logic is that? > You keep assuming that it's HN staff, It's HN staff, and I've already explained it. Read back.
It's quite possible that there are just people flagging things without commenting. I do this all the time if the discussion looks particularly stupid, unproductive, bad-tempered, pointless, and so on - or some combination thereof. (I haven't done it in this case, but only because I was silly enough to comment. This thread has been quite reasonably flagged, I'd say.) This is part of the how this particular site works.…
> It's quite possible that there are just people flagging things without commenting. I do this all the time if the discussion looks particularly stupid, unproductive, bad-tempered, pointless, and so on - or some combination thereof.
Huh? Wait, really? I never ever once considered to flag an article based on the discussion. I've flagged some articles, which I think are bad (as articles).
What's the reasoning behind doing that?
edit: hmph, probably the same reasoning as my reasons to flag, but considering the submission with comments as a whole, instead of the article.
Still, I don't think that some bad comments made by some haters should be enough to remove a good article with several separate good discussions.
edit2: the news guideline[0] is pretty clear about what is a good submission and what is not:
> Hacker News Guidelines
> What to Submit
> On-Topic: Anything that good hackers would find interesting. That includes more than hacking and startups. If you had to reduce it to a sentence, the answer might be: anything that gratifies one's intellectual curiosity.
XLibre having haters that flag it, or randomly appear calling the creator jerk, arsehole, nutjob and more should not be connected for it to be hidden--according to the guidelines, that is. The only remaining option is deliberate censorship I believe.