linux-kernel - Wayland Vulkan X Graphics Kawai Etc.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <0de29311-c614-4c5a-a08b-98ecb7541472@bit-philosophy.net>
Date: Tue, 4 Mar 2025 11:04:10 +0100
From: Ywe Cærlyn <ywe@...-philosophy.net>
To: linux-kernel@...r.kernel.org
Subject: Wayland Vulkan X Graphics Kawai Etc.

Light.

I thought I'd share also some thoughts on Wayland, Vulkan X, Graphics, 
Kawai etc.

Wayland has become rumoured a big thing. It uses a W symbol. Compared to 
X, X is a good symbol for GUI design and exposed APIs.

Such as in Bit X, where Bit is how to design inner loop, related kernel 
constructs etc.

I now also added a Kawai O with I in it, as symbol for Bit X.

Shouldn´t it be best and symbolworld wise, to keep the X, and rather 
integrate the other efforts?

I also hear one "timestamps" each frame here. To allow recording of 
streams etc. Would it not be better to allow producernode to determine 
if one should record or not?

With jitter below 200uS one does not really need timestamping.

If the intention was to reduce jitter, or codeobscurity I agree with 
that. Not if it increases jitter or obscurity in general.

Kawai has become a big thing in games. I think this is good, and I do 
not agree with gunviolence in games aswell (questioning american 
gunlobbies who point to muslos as the problem), preferring the Kawai style.

One can also refer the prophet Ilyas for Kawai, Graphics APIs etc, for a 
complete and tight version of things.

This is fair pay compliant, (as my discussions often are about) and 
recommended.

Light,
https://bit-philosophy.net/