md8z

25 ms·

211.
by md8z 5y ago
I don't see why you would need an X extension, WebGPU works fine within a browser. You don't need to touch X or Wayland or Mesa or anything.
212.
by md8z 5y ago
Yes. KDE has been slowly adopting it for 11 years (!) now: https://aseigo.blogspot.com/2010/10/plasma-in-18-24-months.h...
213.
by md8z 5y ago
That sentence doesn't really make sense to me, did you mean WGSL translates 1:1 to SPIR-V? "WebGPU" refers to the API, not the shading language.
214.
by md8z 5y ago
Maybe you are looking at it in a skewed way. I don't think there is a real use case for "Wayland-native" apps. There is no reason to do that unless you're building an embedded device or something, in which case you alrea
215.
by md8z 5y ago
Yeah, because people were using that for some older Qt Widgets apps. AFAICT it was never supported for Qt Quick because that doesn't even use the Qt platform style.
216.
by md8z 5y ago
I'm very confused by this comment, SPIR-V is not a wire protocol for Vulkan. And you can't really serialize Vulkan over the network, that breaks things like vkMapMemory. If you want something like a remote Vulkan, the thing to wat
217.
by md8z 5y ago
I'd advise against using hyperbole and dismissing projects as "pure garbage". I tried to ask you this before but I would be really interested to know what your use case for motif is in 2021. That seems like a recipe for pain
218.
by md8z 5y ago
I would be really interested to know why people seem to think D-Bus is a "Linuxism". It's a pretty small daemon with an Apache-style license and upstream support for BSD. The only thing I've heard are comments like this
219.
by md8z 5y ago
Qt has Qt Quick and QGraphicsScene which will use a GL backend. GTK4 has a GL backend by default. Web browsers and Electron use Skia which has GL and Vulkan backends. Pretty much every video game is using GL and Vulkan already, or Proton wh
220.
by md8z 5y ago
The GNOME compositor does actually use D-Bus and it is actually much easier to use D-Bus in it than to add new wayland extensions.
221.
by md8z 5y ago
"These issues are irrelevant for connection-oriented and reliable unix sockets." This comment is really confusing to me. It's not irrelevant, you need to serialize the messages somehow. And if you ever decide you want to add
222.
by md8z 5y ago
Waypipe isn't relevant in this case, this post is about remotely invoking an RPC call over D-Bus. It's actually pretty trivial to forward a D-Bus socket using ssh -L.
223.
by md8z 5y ago
That's what XWayland is for, those clients probably will be able to keep working. As long as those clients exist then we'll be able to keep having things like XWayland and XQuartz, it's just translating X11 to the underlying
224.
by md8z 5y ago
IIRC that only applies to Qt Widgets apps which is a decreasing number of apps. The XCB native painting flag doesn't work with Qt Quick and actually seems to break those apps which use it, because Qt Quick is rendered with GL. Someone
225.
by md8z 5y ago
Yeah, indirect GLX is limited to OpenGL 1.4 and earlier. It also isn't even enabled by default on recent Xorg releases, you have to opt-into it.
226.
by md8z 5y ago
What exactly does "native" mean on BSD here? In my experience, that usually just means something that is written in C, uses BSD make, uses the BSD license, and follows some patterns used in the BSD libc. Which seems to apply to ve
227.
by md8z 5y ago
That article wasn't really accurate, most clients aren't using the X drawing commands anymore. The "vast majority of cases" has moved to using GL or Vulkan, which also doesn't serialize over the network.
228.
by md8z 5y ago
Maybe you were using the wayland backend, you might have to force X11 with the environment variable "GDK_BACKEND=x11". Though part of this weirdness is due to the clunkiness of the way X forwarding is implemented, I wish there was
229.
by md8z 5y ago
There isn't much for me to say. To be honest, I would probably not contribute to that website. Wayland isn't that exciting of a technology and I don't think end users should even need to care about it or care that any of thos
230.
by md8z 5y ago
I'm not sure what you mean 1GB. An empty tab on Chromium seems to take about 30MB. Minimal "Hello world" GTK and Qt programs are around the same size. Modern Xorg is also using the KMS API. If you don't want any fancy fe
231.
by md8z 5y ago
Is it? The HN front page absolutely does have some level of algorithmic manipulation going on. There was just a thread on this: https://news.ycombinator.com/item?id=29024032
232.
by md8z 5y ago
I see this sentiment posted often on HN but I've seen no social media that didn't eventually become toxic or that didn't feed on human attention, this website included. What good is a platform if nobody pays attention to it?
233.
by md8z 5y ago
"But, what if we have a protocol where you simply open a network socket and write some messages on it that says 'write this text hear', 'draw a line from X to Y'? Well, that is how X clients work." I mean, that
234.
by md8z 5y ago
7-8x speedup is not really that much when parallelized GPU algorithms can usually get 100x speedup or more. I would suggest to look at benchmarks compared to GPU based solutions such as piet-gpu, or even a parallelized 2d renderer like Blen
235.
by md8z 5y ago
The GPU acceleration in Glamor doesn't really help, the issue here is that everything still needs to be serialized by the X protocol, rather than being drawn in parallel as they would on a GPU. Edit: There has been some progress on GPU
236.
by md8z 5y ago
"What I like about X, that is missing in Wayland, is that you no longer can run the X server on a machine and connect to clients (application) on another." You actually can do this with Waypipe. Also, I'll mention this again:
237.
by md8z 5y ago
That will continue to work in Wayland, they haven't broken X forwarding. It works similarly to how XQuartz works on the mac.
238.
by md8z 5y ago
Sorry, I should have been more clear. I think Myspace was the end-result of that era if you followed it to its logical conclusion.
239.
by md8z 5y ago
Wayland is a protocol specifically for compositing window managers, the point of it was to simplify the implementation of window managers that already existed as X compositors, e.g. Mutter, KWin, Enlightenment. If other window managers were
240.
by md8z 5y ago
The stuff that's not backwards compatible in XWayland is mostly already broken by X compositors anyway and needed to be reimplemented, so that's why there wasn't much incentive to fix that. I've seen some of your comment

More ›