wayland

When I'm evaluating an open-source project, I always check the quality of its commit messages. I don't care about following a specific format or something, all that matters is whether they are informative or not. Sadly, Odin doesn't seem to pass the test. It's full of commits labeled with just "fix <thing>": https://github.com/odin-lang/Odin/commits/master A few examples of projects with better commit messages: Linux kernel: https://github.com/torvalds/linux/commits/master gcc: https://github.com/gcc-mirror/gcc/commits/master Perl: https://github.com/Perl/perl5/commits/blead Wayland: https://github.com/wayland-project/wayland/commits/main

gammastep can control wayland colour temperatures;. Other compositors and applications can access the same protocols. Wayland (proto) supports 16bits per colour. (Much more than HDRs 10 bit) https://github.com/wayland-project/wayland/blob/6741dafbf7a5... It’s up to the compositor to enable them.

> But now that you mention it, it's true that wayland was stagnating and that when Mir arrived, everything accelerated. Sometime having a common enemy is a good motivator. This seems to be something a lot of people believe, but when you look at the history of it all it's really not the case.[1] I have a feeling it's because the controversy sparked a number of articles which talked about things in a more public way which made it feel like Wayland was suddenly making progress after stagnation, while in actuality development pace was chugging along as it always had been. [1] Canonical announced Mir early 2013[2], you'll notice there is no great spike around that time in any of: [1a] the Wayland repo https://github.com/wayland-project/wayland/graphs/code-frequ... [1b] the weston repo: https://github.com/wayland-project/weston/graphs/code-freq