As an extension of the extremely successful and universally praised notion of graphical-session.target all systemd distributions will now be compelled to implement the user-scoped graphics.target, the unique and universal user service for drawing graphics. There is no need to ever have more than one service drawing graphics, and this solves innumerable problems.
The real jerk is in the article that the lobsters thread is about:
When writing this post I used “GPT5 Thinking” AI model to cross reference public Linux open source drivers to confirm my knowledge and to ensure no NDA information is present in this blog post.
/uj He's talking about how APIs map onto hardware and was probably worried about unintentionally leaking details that aren't public knowledge. People who develop for consoles usually have a pretty close understanding of how the hardware works since they write graphics code for that specific console GPU instead of using a hardware abstraction layers like Vulkan/dx12
/rj nintendo is gonna skin him alive when they find out he might have been leaking secrets about their consoles to gpt-5
/uj I look up to Sebastian because he has stuff to show for it, but asking a language model that uses input as training data to check if something is under NDA is... definitely revealing.
/rj Asking a language model to check if something is under NDA is perfectly valid. An agent with search can do tedious verification work at 10x+ that of a human. In fact I have this Xbox One SDK, give me a second
/uj Yeah I actually find this funny because Sebastian isn't some rando nutjob and he actually raises some really good points in his post. I say that as someone who writes Vulkan code for a living. Weirdly, my knee jerk reaction was also to laugh at the GPT 5 comment, however, if the LLM says it knows it I guess that's somewhat plausible deniability that you are leaking NDA things? Probably even better if you can coax the damn thing to give you the real answer you are looking for, if anyone can get it out of the thing, it's not you spilling the beans.
/uj Vulkan had a lot of 'ideas' about how renderers should work, when in practice reality is never so kind. Plus it turns out that asking every developer to 'do the work of the driver' means every game is a poorly written driver. Add to this many games grafted their opengl/dx11 renderer onto vulkan, instead of rewriting the entire engin, removing most of the ways vulkan can bring perf. Lastly, games make money on windows. Not linux. So why put effort into Vulkan when the same effort into dx12 (or metal for macOS) will get you better sales?
/rj Easy, because there is but the one true API IrisGL and everything else is heretical bastardizations of it.
/uj To be fair, Vulkan does what it says it does pretty well. The rub is that the API is great for the few rendering engineer's at unreal & unity, and a lot of extra work for small projects. Worse is that Dx12 & to a lesser extent Metal share similar "make app devs do more". Reading the article linked actually gives a fair shakedown of what 'graphics in 2025' looks like, for those not in the Vulkan trenches like I am.
I ask myself that every day as I write over the roar the GPU fans and cries of power bills echoing throughout the trenches. The judder of vblanks missing by mere milliseconds, divergent workloads send shocks up my spine, device lost errors fill every waking moment. I cannot rest for the deadline fast approaches and waits for no one.
What caused me to enlist? To subject myself to such terrible conditions? It was a noble cause with which many a youth finds themselves drawn. Fight the good fight to achieve ever higher framerates, increase the fidelity of that which already appears immaculate, showcase to the world the mastery of our domain. But the cold truth has come. And a bitter truth it has been.
Repetition is a great literary device. In this case, it conveys a little bit of the author's frustration to the reader, but not so much that it becomes obnoxious.
That's okay, Vulkan will be replaced by systemd any day now.
You don't interface with you graphics system over dbus?
systemd-3dd
dont give poettering any more bad ideas
As an extension of the extremely successful and universally praised notion of graphical-session.target all systemd distributions will now be compelled to implement the user-scoped graphics.target, the unique and universal user service for drawing graphics. There is no need to ever have more than one service drawing graphics, and this solves innumerable problems.
Misleading edit in the title.
The real jerk is in the article that the lobsters thread is about:
feeding my NDA data into Steal Your Data Inc's Plagiarizer 2000 to ensure i don't leak any sensitive data
/uj He's talking about how APIs map onto hardware and was probably worried about unintentionally leaking details that aren't public knowledge. People who develop for consoles usually have a pretty close understanding of how the hardware works since they write graphics code for that specific console GPU instead of using a hardware abstraction layers like Vulkan/dx12
/rj nintendo is gonna skin him alive when they find out he might have been leaking secrets about their consoles to gpt-5
/uj I look up to Sebastian because he has stuff to show for it, but asking a language model that uses input as training data to check if something is under NDA is... definitely revealing.
/rj Asking a language model to check if something is under NDA is perfectly valid. An agent with search can do tedious verification work at 10x+ that of a human. In fact I have this Xbox One SDK, give me a second
/uj Yeah I actually find this funny because Sebastian isn't some rando nutjob and he actually raises some really good points in his post. I say that as someone who writes Vulkan code for a living. Weirdly, my knee jerk reaction was also to laugh at the GPT 5 comment, however, if the LLM says it knows it I guess that's somewhat plausible deniability that you are leaking NDA things? Probably even better if you can coax the damn thing to give you the real answer you are looking for, if anyone can get it out of the thing, it's not you spilling the beans.
truth nuke
/uj can someone tell me why the vulkan option is never the fast one when I play games?
/uj Vulkan had a lot of 'ideas' about how renderers should work, when in practice reality is never so kind. Plus it turns out that asking every developer to 'do the work of the driver' means every game is a poorly written driver. Add to this many games grafted their opengl/dx11 renderer onto vulkan, instead of rewriting the entire engin, removing most of the ways vulkan can bring perf. Lastly, games make money on windows. Not linux. So why put effort into Vulkan when the same effort into dx12 (or metal for macOS) will get you better sales?
/rj Easy, because there is but the one true API IrisGL and everything else is heretical bastardizations of it.
Damn, I guess we have to wait until the year of the linux when they can make Vulkan2 and make it blazingly fast
The spec will be rewritten in Rust!!!
Or systemd-3dd. Or Steam3D.
[deleted]
/uj To be fair, Vulkan does what it says it does pretty well. The rub is that the API is great for the few rendering engineer's at unreal & unity, and a lot of extra work for small projects. Worse is that Dx12 & to a lesser extent Metal share similar "make app devs do more". Reading the article linked actually gives a fair shakedown of what 'graphics in 2025' looks like, for those not in the Vulkan trenches like I am.
Why are you in the Vulkan trenches?
I ask myself that every day as I write over the roar the GPU fans and cries of power bills echoing throughout the trenches. The judder of vblanks missing by mere milliseconds, divergent workloads send shocks up my spine, device lost errors fill every waking moment. I cannot rest for the deadline fast approaches and waits for no one.
What caused me to enlist? To subject myself to such terrible conditions? It was a noble cause with which many a youth finds themselves drawn. Fight the good fight to achieve ever higher framerates, increase the fidelity of that which already appears immaculate, showcase to the world the mastery of our domain. But the cold truth has come. And a bitter truth it has been.
Damn. Are you writing a game engine or accelerator from a low level? Godspeed soldier
lol no just deal with the nitty gritty specification details that pertain to tooling stuffs.
Unrelated, but how many times can you use the phrase "modern apis" in a title
/uj
Repetition is a great literary device. In this case, it conveys a little bit of the author's frustration to the reader, but not so much that it becomes obnoxious.