This is the
talk page for discussing improvements to the
Wayland (protocol) article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google ( books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
Archives: 1Auto-archiving period: 90 days |
This article is rated C-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||
|
The article only talks what things replace which other things, and who is committed to port which projects to Wayland. But why is it beneficial? What is the functionality that is impossible, or very difficult to implement, today and will be possible with Wayland? What is the end user benefit? It only says "offering more flexibility and better performance", but what flexibility, why performance benefit and how? For example, I use gnome and kde desktops, many visual apps. Windows transparency works and many very fancy windows effects all work. What will I gain with Wayland? Article doesn't have much, and reader of this article is left wondering why this thing is out there? I only read this article, and I am not even convinced this is a good thing, except it will avoid extra copies of some buffers and will get some performance benefit because of this. Article reads like this is a reshuffling of existing functional blocks with unclear benefits. Yurivict ( talk) 10:36, 27 January 2012 (UTC)
In the releases section, under 1.13, it says: "The ABI of Weston has been changed, thus the new version was named 2.0.0 rather than 1.13.0" If the new version was named 2.0.0 instead of 1.13.0, why is the table entry for the version is still 1.13 ? — Preceding unsigned comment added by 199.246.40.56 ( talk) 21:05, 23 November 2017 (UTC)
I would suggest to remove the preview version as I'm not sure anyone who's not an expert on wayland will use it. And if they are an expert on wayland, they would know what and where the preview version is. And people seem to not update the preview version on wikipedia frequently enough. Maltimore ( talk) 10:01, 8 April 2020 (UTC)
I find this page very difficult for the average reader to understand. I am not planning to make any immediate edits but article reads very much like it was written by a coder as opposed to a layman and it is evident.
I hope to make some changes to this page in the near future but if there are any other wiki editors with more time than myself right now I would appreciate it if they could distil the text for a lay audience. — Preceding unsigned comment added by 0lida0 ( talk • contribs) 01:27, 6 October 2021 (UTC)
Much of the content of this page describes the situation as of 2014 or so. Is it possible to bring it up to date? m.e. ( talk) 02:35, 17 May 2022 (UTC)
This article lacks the criticisms of Wayland as well as its advantages and disadvantages compared to X11. It would be nice if someone with enough expertise could add this. 157.143.15.229 ( talk) 20:42, 30 September 2022 (UTC)
This is the
talk page for discussing improvements to the
Wayland (protocol) article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google ( books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
Archives: 1Auto-archiving period: 90 days |
This article is rated C-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||
|
The article only talks what things replace which other things, and who is committed to port which projects to Wayland. But why is it beneficial? What is the functionality that is impossible, or very difficult to implement, today and will be possible with Wayland? What is the end user benefit? It only says "offering more flexibility and better performance", but what flexibility, why performance benefit and how? For example, I use gnome and kde desktops, many visual apps. Windows transparency works and many very fancy windows effects all work. What will I gain with Wayland? Article doesn't have much, and reader of this article is left wondering why this thing is out there? I only read this article, and I am not even convinced this is a good thing, except it will avoid extra copies of some buffers and will get some performance benefit because of this. Article reads like this is a reshuffling of existing functional blocks with unclear benefits. Yurivict ( talk) 10:36, 27 January 2012 (UTC)
In the releases section, under 1.13, it says: "The ABI of Weston has been changed, thus the new version was named 2.0.0 rather than 1.13.0" If the new version was named 2.0.0 instead of 1.13.0, why is the table entry for the version is still 1.13 ? — Preceding unsigned comment added by 199.246.40.56 ( talk) 21:05, 23 November 2017 (UTC)
I would suggest to remove the preview version as I'm not sure anyone who's not an expert on wayland will use it. And if they are an expert on wayland, they would know what and where the preview version is. And people seem to not update the preview version on wikipedia frequently enough. Maltimore ( talk) 10:01, 8 April 2020 (UTC)
I find this page very difficult for the average reader to understand. I am not planning to make any immediate edits but article reads very much like it was written by a coder as opposed to a layman and it is evident.
I hope to make some changes to this page in the near future but if there are any other wiki editors with more time than myself right now I would appreciate it if they could distil the text for a lay audience. — Preceding unsigned comment added by 0lida0 ( talk • contribs) 01:27, 6 October 2021 (UTC)
Much of the content of this page describes the situation as of 2014 or so. Is it possible to bring it up to date? m.e. ( talk) 02:35, 17 May 2022 (UTC)
This article lacks the criticisms of Wayland as well as its advantages and disadvantages compared to X11. It would be nice if someone with enough expertise could add this. 157.143.15.229 ( talk) 20:42, 30 September 2022 (UTC)