PJpjmlp·Mar 20, 2019Submission
Google Games Platform Vulkan Extensions
2 points · Open discussionKhronosGroup
Vulkan-Docs
JavaScript2016–2026
KhronosGroup / Vulkan-Docs
Vulkan-Docs
The Vulkan API Specification and related tools
19Distinct people
23Mentions
1Explicit recommenders
3.4KGitHub stars
What to know before exploring
What it is
The Vulkan API Specification and related tools
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
To answer that question in the context of Vulkan I highly recommend reading the proposal document for VK_EXT_shader_object which contains a great explanation in the problem…
CrossVR used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 6:01:08 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year23 dated mentions
Observed mentions: 2016-02-16 14:01:37 UTC to 2026-02-13 17:27:50 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 5 | 2 | 3 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
2 sources> There are two approaches to this endorsed by different camps in Wayland: these Wayland protocols, and a dbus protocol based on Pipewire.
Pipewire approach looks the best for screenshots and video recording. I hope all Wayland compositors will settle on it.
> Secondary clipboard support <...> wp-primary-selection
I guess the standard is very recent. Last time I tried, KWin didn't support it yet.
> We fought long and hard over this and we now have a protocol for negotiating client- vs server-side decorations, which is now fairly broadly supported, including among some of its opponents.
A major problem with Mutter remains. Mutter developers don't want to depend on GTK for whatever reason, but so are SDL, mpv and other non-GUI applications and toolkits developers. The result are ugly looking windows for such cases in Gnome.
> You have to s
Read the rest
tep up, though: no one working on Wayland today seems to care.
It's a problem with Wayland in general. The end user gets the short end of the stick, since with removal of some functionality that was in X, some use cases are cut off. But there is no one player like with X server. Tons of compositors are developed by different people. So even raising the issue let alone coming to some consensus takes a very long time.
I'm not saying Wayland isn't the way to go, just pointing out it's a very hard transition.
> Wayland doesn’t support Nvidia!
How is the progress of using Vulkan for Wayland compositors and avoiding the whole EGLstreams mess?
I see this: https://github.com/KhronosGroup/Vulkan-Docs/issues/294
But it's not clear from it whether now there is a way to avoid using GBM or EGLstreams.