mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-25 23:11:02 +08:00
translated by cycoe
This commit is contained in:
cycoe
parent
9f6da8948e
commit
b700297314
@ -1,101 +0,0 @@
|
||||
translating by cycoe
|
||||
|
||||
# Fedora 25: Wayland vs Xorg
|
||||
|
||||
Almost as good as Alien vs Predator only much better. Anyhow, as you probably know, I have recently tested [Fedora 25][1]. It was an okay experience. Overall, the distro behaved reasonably well. Not the fastest, but stable enough, usable enough, with some neat improvements here and there. Most importantly, apart from some performance and responsiveness loss, Wayland did not cause my system to melt. But that's just a beginning.
|
||||
|
||||
Wayland is in its infancy as a consumer technology, or at least that thing that people take for granted when they do desktop stuff. Therefore, I must continue testing. Never surrender. In the past few weeks of actively using Fedora 25, I did come across a few other issues and problems, some less worrying, some quite disturbing, some odd, some meaningless. Let us elaborate.
|
||||
|
||||
|
||||
|
||||
Note: Image taken from [Wikimedia][2] and modified, licensed under [CC BY-SA 3.0][3].
|
||||
|
||||
### Wayland does not support everything
|
||||
|
||||
Nope. 'Tis a fact. If you go about a Web, doing some reading, you will have learned that all sorts of things are not yet Wayland-ready. Still, we all know Fedora is the state-of-art bleeding-edge distro, and so it's a testbed for pain and discovery. Fair enough. For a while, things were quite all right, no fuss, no errors, but then, I suddenly needed to use GParted. I was in a hurry, troubleshooting a big issue, and now I had to sidetrack myself with pointless extra work. GParted would just not launch under Wayland. Exploring in a bit more detail, I learned that this partitioning software was not supported yet.
|
||||
|
||||
|
||||
|
||||
And the thing is, I do not really know what other applications do not work under Wayland, and I am not really keen to discover that in a moment of true reckoning. Searching online, I wasn't able to find a quick, easy list that details the current incompatibilities. Maybe it's me, and I suck at searching, but something as trivial as "Wayland + compatibility" should be obvious.
|
||||
|
||||
What I did find is a [self-argument][4] telling us why Wayland is good, a list of [Gnome][5] applications currently supported under this new thingie, several nerdy pages on ArchWiki, a super-nerdy slit-my-wrists topic on [Nvidia][6]devtalk, and a few other ambiguous discussions.
|
||||
|
||||
### Performance, again
|
||||
|
||||
On the Fedora 25 box, I changed the login session from Gnome (Wayland) to Gnome Xorg, to see how this affects the system. I didpreviously mention the performance benchmarks and comparison to [Fedora 24][7] on the same laptop - [Lenovo G50][8], but this should give us even more accurate results.
|
||||
|
||||
Wayland (screenshot 1) gives us 1.4GB memory use without anything else running, and the CPU averages about 4-5%. Xorg (screenshot 2) tolls the same amount of RAM, and the processor eats 3-4% of its full power. Marginally less in sheer numbers. But then, the experience in the Xorg session is just so much better. It's milliseconds alright, but you can feel it. The legacy session seems to be ever so slightly sprightlier, faster, fresher. The lag is less noticeable. If you are sensitive as to how your desktop responds, you will not be happy with this penalty. Sure, this may only be a bit of sub-optimized beginner's luck, and Wayland may improve over time. But it's also something we cannot ignore.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Let's rant
|
||||
|
||||
I am not happy with this. Not massively angry, but I don't like that I actually need to login into the classic X session to be able to fully enjoy my desktop experience. Because X gives me 100%. Wayland does not. That means, at the end of the day, I will not be using Wayland. I like exploring technology, but I am not a zealot on some holy big-endian pilgrimage. I just want to use my desktop, and sometimes, I might even need things fast. Logging out and back in can be an annoying hassle in a moment of need. And the reason why we have this issue is because Wayland is not there to make life easier for Linux desktop users. Quite the opposite. Quote:
|
||||
|
||||
Wayland is intended as a simpler replacement for X, easier to develop and maintain. GNOME and KDE are expected to be ported to it.
|
||||
|
||||
And you see, that's part of the problem. Stuff should not be designed to be easier to developer or maintain. That can be a beneficial by-product provided all other customer requirements are met. But if they are not, then it does not matter how hard or simple it is for programmers to hammer code. That's their job. The whole purpose of technology is to support the end state - in this case, a seamless and smooth user experience.
|
||||
|
||||
Unfortunately, a large number of products today are being re-invented and re-developed for the sake of making it easier for software people and not for the users. To a large extent, Gnome 3, PulseAudio, [Systemd][9], and Wayland, they all serve no higher user experience purpose. They are quite intrusive in that sense, and they do not contribute to the stability and simplicity of the Linux desktop ecosystem.
|
||||
|
||||
This is one of primary reasons why Linux desktop is a relatively immature product - it is designed to self-support the people developing it, almost like a living organism. It's not there to be the slave to the whims and wishes of the user. And that's how great things are done. You satisfy the primary need, and only then worry about the details. Great user experience does not depend - and should never depend - on the choice of programming language, compiler or any nonsense like that. If it does, that whoever designed the product has not done the abstraction piece well enough, and we have a failed thing that needs to be removed from existence.
|
||||
|
||||
And so, from my perspective, I don't care if it takes 10 liters of blood to compile one version of X or whatever. I'm a user. All I care is that my desktop works as robustly as did it yesterday or 5 years ago. If that's not happening, I'm not interested in macros, classes, variables, declarations, structs, or any other geeky CS technobabble. That's irrelevant. And a product that advertises itself as being created to be convenient for the people developing it is a paradox. Don't develop it, then. Makes things even easier.
|
||||
|
||||
Now, the reality is, Wayland is largely ok - but it is still not as good as X, and as such it should not be offered as a production-ready item on any desktop. Once it can replace the old technology so seamlessly no one ever knows about it, only then will it have succeeded in what it needs to achieve, and then, it can be written in C or D or K language, and it can have anything the developers want. Until then, it's a parasite that eats on the resources and peoples' nerves.
|
||||
|
||||
Don't get me wrong. We need progress. We need change. But it has to serve an evolutionary purpose. Does X handle the user needs well today? Can it do graphics support for 3rd party blobs? Can it support HD and UHD and DPI and whatnot? Can you play the latest games on it? Yes? No? If not, then it needs to be fixed. Those are the evolutionary drivers. Not the difficulty of writing and compiling code. Software developers are the coal miners of the digital industry, and they need to work hard to make users happy. As a phrase 'easier to develop' should be outlawed, and people who like it need to be electrocuted by old radio batteries and then exiled to Mars in non-A/C spaceships. If you can't write smart code, it's your problem. The user should not suffer because developers think they're princesses.
|
||||
|
||||
### Conclusion
|
||||
|
||||
Here we are. In general, Wayland is not bad. It's okay. But that's like saying you are earning 83% today compared to 100% yesterday only because someone decided to change the layout of your payslip. Not acceptable in that sense, even if Wayland works fairly well. It's the stuff that does not work that makes all the difference. Ignoring the whole rant side of it, Wayland introduced reduced usability, performance and app wise, and this is something Fedora will have to sort out fast.
|
||||
|
||||
Other distros will follow, and we will be seeing a recurring pattern. The same happened with Gnome 3\. The same happened with Systemd. Less than fully ready technologies are unleashed into the open, and then we spend a year or two fixing things that needed no fixing, and eventually, we will have the same functionality we already have, only created in a different programming language. Not interested. CS used to be all glamor in 1999, when Excel users were making USD50/hour. Today, programming is the undeserving oar galley, and people don't care for the sweat and blister under the deck.
|
||||
|
||||
Performance is probably less of an issue, because you can give up on 1-2% change, especially since it can randomly come from any which factor. You will know this if you've used Linux for more than a year or two. But not being able to launch programs is a big deal. At the very least, Fedora graciously offers the legacy platform, too. But then, it may be gone before Wayland reaches 100% maturity. Here we go again. So no, there's no disaster. My original Fedora 25 claim stands in this regard. What we have is annoyance. Unnecessary annoyance. Ah well. The story of Linux, part 9000.
|
||||
|
||||
And so, at the end of the day, with everything said and done, what we learned here is: KNEEL BEFORE XORG! OMG. That's so good, I will now fade into the background while the chuckles off your merriment carry off into the frosty night. So long.
|
||||
|
||||
Cheers.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
|
||||
|
||||
作者简介：
|
||||
|
||||
My name is Igor Ljubuncic. I'm more or less 38 of age, married with no known offspring. I am currently working as a Principal Engineer with a cloud technology company, a bold new frontier. Until roughly early 2015, I worked as the OS Architect with an engineering computing team in one of the largest IT companies in the world, developing new Linux-based solutions, optimizing the kernel and hacking the living daylights out of Linux. Before that, I was a tech lead of a team designing new, innovative solutions for high-performance computing environments. Some other fancy titles include Systems Expert and System Programmer and such. All of this used to be my hobby, but since 2008, it's a paying job. What can be more satisfying than that?
|
||||
|
||||
From 2004 until 2008, I used to earn my bread by working as a physicist in the medical imaging industry. My work expertise focused on problem solving and algorithm development. To this end, I used Matlab extensively, mainly for signal and image processing. Furthermore, I'm certified in several major engineering methodologies, including MEDIC Six Sigma Green Belt, Design of Experiment, and Statistical Engineering.
|
||||
|
||||
I also happen to write books, including high fantasy and technical work on Linux; mutually inclusive.
|
||||
|
||||
Please see my full list of open-source projects, publications and patents, just scroll down.
|
||||
|
||||
For a complete list of my awards, nominations and IT-related certifications, hop yonder and yonder please.
|
||||
|
||||
|
||||
-------------
|
||||
|
||||
|
||||
via: http://www.dedoimedo.com/computers/fedora-25-wayland-vs-xorg.html
|
||||
|
||||
作者：[Igor Ljubuncic][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://www.dedoimedo.com/faq.html
|
||||
|
||||
[1]:http://www.dedoimedo.com/computers/fedora-25-gnome.html
|
||||
[2]:https://commons.wikimedia.org/wiki/File:DragonCon-AlienVsPredator.jpg
|
||||
[3]:https://creativecommons.org/licenses/by-sa/3.0/deed.en
|
||||
[4]:https://wayland.freedesktop.org/faq.html
|
||||
[5]:https://wiki.gnome.org/Initiatives/Wayland/Applications
|
||||
[6]:https://devtalk.nvidia.com/default/topic/925605/linux/nvidia-364-12-release-vulkan-glvnd-drm-kms-and-eglstreams/
|
||||
[7]:http://www.dedoimedo.com/computers/fedora-24-gnome.html
|
||||
[8]:http://www.dedoimedo.com/computers/lenovo-g50-distros-second-round.html
|
||||
[9]:http://www.ocsmag.com/2016/10/19/systemd-progress-through-complexity/
|
||||
98
translated/tech/20170210 Fedora 25 Wayland vs Xorg.md
Normal file
98
translated/tech/20170210 Fedora 25 Wayland vs Xorg.md
Normal file
@ -0,0 +1,98 @@
|
||||
# Fedora 25: Wayland 大战 Xorg
|
||||
|
||||
就像异形大战铁血战士一样，后者略胜一筹。不管怎样，你可能知道，我最近测试了 [Fedora 25][1]，体验还可以。总的来说，这个发行版表现的相当不错。它不是最快速的，但随着一系列的改进，变得足够稳定也足够可用。最重要的是，除了一些性能以及响应性的损失，Wayland 并没有造成我的系统瘫痪。但这还仅仅是个开始。
|
||||
|
||||
Wayland 作为一种消费者技术还处在它的襁褓期，或者至少是当人们在处理桌面事物时应理所当然的这么认为。因此，我必须继续测试，绝不弃坑。在过去的积极地使用 Fedora 25 的几个星期里，我确实碰到了几个其他的问题，有些不用太担心，有些确实很恼人，有些很奇怪，有些却无意义。让我们来讲述一下吧！
|
||||
|
||||
|
||||
|
||||
注: 图片来自 [Wikimedia][2] 并做了些修改, 证书为 [CC BY-SA 3.0][3].
|
||||
|
||||
### Wayland 并不支持所有软件
|
||||
|
||||
当然不，这是一个事实。如果你去网站上阅读相关的信息，你会发现各种各样的软件都还没为 Wayland 做好准备。但是，我们都知道 Fedora 是一个激进的高端发行版，所以它是为了探索新功能的测试床。这很公平。有一段时间，所有东西都很正常，没有瞎忙活，没有错误。但接下来，我突然需要使用 GParted。我当时很着急，正在排除一个大故障，然后我不得不让自己侧重于无意义的额外工作。 GParted 没办法在 Wayland 下直接启动。在探索了更多一些细节之后，我知道了分区软件目前还没有被支持。
|
||||
|
||||
|
||||
|
||||
问题就在于我并不太清楚其他哪些应用不能在 Wayland 下运行，并且我不能在一个正确估计的时间敏锐地发现。通过在线搜索，我还是不能找到一个目前的简要的不兼容列表。可能只是我，在搜索中遇到了困难，但显然的是一定有什么东西和 "Wayland + 兼容性" 一样琐碎。
|
||||
|
||||
我已经找到的是一个告诉我们 Wayland 很棒的[自我评论][4]，一个目前已被这个新玩意儿支持的 [Gnome][5] 应用程序列表，一些 ArchWiki 上的死板的资料，一个在 [英伟达][6] 开发论坛上的呆板得让我后悔点进去的主题，以及一些其他含糊的讨论。
|
||||
|
||||
### 再次提到性能
|
||||
|
||||
在 Fedora 25 上，我把登录会话从 Gnome（Wayland）切换到 Gnome Xorg，观察会对系统产生什么影响。我之前已经提到过在同一个笔记本（[联想 G50][8]）上的性能跑分和与 [Fedora 24][7] 的比较，但这次会给我们提供更加准确的结果。
|
||||
|
||||
Wayland（截图 1）空闲时的内存占用为 1.4GB， CPU 的平均负载约为 4-5%。Xorg（截图 2）占用了同样大小的内存，处理器消耗了全部性能的 3-4%，单纯从数字上来看少了一小点。但是 Xorg 会话的体验却好得多。虽然只是毫秒级，但你感受的到差距。传统的会话看起来更加的灵动、快速、清新一点。但（Wayland）落后并不明显。如果你对你的电脑响应速度很敏感，你可能不会对这点延迟满意。当然，这可能只会成为新手的一点点优化措施，Wayland 会随时间进步。但它也是我们所不能忽视的。
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### 杂谈
|
||||
|
||||
我对此并不高兴。并不是很愤怒，但我不喜欢为了能完全享受我的桌面体验，我却需要登录到传统的 X 会话。因为 X 给了我 100%，但 Wayland 没有。这意味着在一天结束的时候，我不是在用着 Wayland。我喜欢探索科技，但我不是一个盲目的狂热追随者。我只是想用我的桌面，有时我可能需要它快速响应。注销然后重新登录在急需使用的时候会成为恼人的麻烦。我们遇到这个问题的原因就是 Wayland 没有让 Linux 桌面用户的生活变得更简单，而恰恰相反。引用：
|
||||
|
||||
> Wayland 是为了成为 X 的更加简单的替代品，更加容易开发和维护。建议 GNOME 和 KDE 都使用它。
|
||||
|
||||
你能看到，这就是问题的一方面原因。东西不应该被设计成容易开发或维护。它能成为所有其他消费需求碰撞后提供的有益的副产品。但如果它们不是，那么不管它对于程序员敲代码来说多么困难或简单都将不重要。那是他们的工作。科技的所有目的都是为了达到一种无缝并且流畅的用户体验。
|
||||
|
||||
不幸的是，现在很大数量的产品都被重新设计或者开发，只是为了使软件人员更加轻松，而不是用户。在很大程度上，Gnome 3、PulseAudio、[Systemd][9] 和 Wayland 都没有遵循提高用户体验的宗旨。在这个意义上来说，它们更像是一种侵略，而没有为 Linux 桌面生态的稳定性和易用性作出贡献。
|
||||
|
||||
这也是为什么 Linux 桌面是一个相对不成熟产品的一个主要原因————它被设计成开发人员的自我支持产品，更像一个活生生的生物。而不是依附于用户各种怪念头和想法的奴隶。这也是伟大事物是如何形成的。你满足于主要需求，接下来只是担心细节方面。优秀的用户体验不依赖于（也永远不依赖于）编程语言、编译器的选择，或任何其他无意义的东西。如果依赖了，那么不管谁来设计这个抽象层做的不够好的产品，我们都会得到一个失败的作品，需要把它的存在抹去。
|
||||
|
||||
那么在我的展望中，我不在乎是否要花费 10 升心血，或其他的什么，去编译一个版本。我是一个用户，我所在乎的只是我的桌面能否像它昨天或者 5 年前一样健壮地工作。如果没发生那种事，我不会对宏、类、变量、声明、结构体，或其他任何极客的计算机科技感兴趣。那是不着边际的。一个产品宣传自己是被创造出来为人们的开发提供方便的，那是个悖论。接下来也不用去开发它了。这样反而会使事情更简单。
|
||||
|
||||
现在，事实是 Wayland 大体上可用，但它仍然不像 X 那么好。并且它也不应该在任何的桌面上作为就绪的产品被提供。一但它能够无缝取代那人们没听说过的过时技术，到那时，它能够在它需要去实现的目标取得成功。然后，它能够用 C、D 或者 K 语言重写，拥有开发者需要的任何东西。在那之前，它都是一个蚕食资源和人们思想的寄生虫。
|
||||
|
||||
不要误会，我们需要进步，需要改变。但它不得不为了进化的目而服务。现在 X 能很好地掌握用户需求了吗？它能为第三方库提供图形支持吗？它能支持 HD、UHD、DPI 或其他的什么吗？你能用它玩最新的游戏吗？是或否？如果不能，那么它需要被修复。这些就是进化的驱动力。而不是写代码或者编译代码的困难程度。软件开发者是数字工业的矿工，他们需要努力工作来使用户开心。就像短语“更加易于开发”应该被取缔一样，那些崇尚于此的人也应该用老式收音机的电池处以电刑，然后用没有空调的飞船流放到火星上去。如果你不能写出高明的代码，那是你的问题。用户不能因为开发者认为自己是公主而遭受折磨。
|
||||
|
||||
### 结语
|
||||
|
||||
说到这里。大体上说，Wayland 还可以，并不差。但这说的就像是某人决定修改你工资单上的布局，导致你从昨天能赚 100% 到今天只能赚 83% 一样。讲道理这是不能接受的，即使 Wayland 工作的相当好。正是那些不能运作的东西导致如此大的不同。忽略所有数落它的一方， Wayland 被认为的降低了可用性、性能以及软件的知名度，正是 Fedora 亟待解决的问题。
|
||||
|
||||
其他的发行版会跟进，然后我们会看到一个循环的模式，就像 Gnome 3 和 Systemd 所发生的一样。没有完全准备好的东西被放到开放环境中，然后我们花费一两年时间修复无需修复的东西，最终我们将拥有我们已经拥有的相同功能，只是用不同的编程语言来实现。我并不感兴趣。计算机科学曾在 1999 年非常受欢迎，当时 Excel 用户每小时能赚 50 美元。现在，编程就像是躲在平底船下划桨，人们并不会在乎你在甲板下流下的汗水与磨出的水泡。
|
||||
|
||||
性能可能已经不是一个问题，因为你可以放弃 1-2% 的变化，尤其是它会受随机的来自任何一个因素的影响。如果你已经用 Linux 超过一、两年你就会知道的。但是无法启动应用是个大问题。至少 Fedora 也友好地提供了传统的平台。但是，它可能会在 Wayland 100% 成熟前就消失了。我们再来看看，不，不会有灾难。我原本的 Fedora 25 宣称支持这种看法。我们有的就是烦恼，不必要的烦恼。啊，这是 Linux 故事中的第 9000 部。
|
||||
|
||||
那么，在今天结束之际，我们已经讨论了所有事情。从中我们学到：臣伏于 Xorg！天呐！真棒，现在我将淡入背景，而笑声会将你的欢乐带给寒冷的夜晚。再见！
|
||||
|
||||
干杯。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
|
||||
作者简介：
|
||||
|
||||
我是 Igor Ljubuncic。现在大约 38 岁，已婚但还没有孩子。我现在在一个大胆创新的云科技公司做首席工程师。直到大约 2015 年初，我还在一个全世界最大的 IT 公司之一中做系统架构工程师，和一个工程计算团队开发新的基于 Linux 的解决方案，优化内核以及攻克 Linux 的问题。在那之前，我是一个为高性能计算环境设计创新解决方案的团队的技术领导。还有一些其他花哨的头衔，包括系统专家、系统程序员等等。所有这些都曾是我的爱好，但从 2008 年开始成为了我的有偿的工作。还有什么比这更令人满意的呢？
|
||||
|
||||
从 2004 年到 2008 年间，我曾通过作为医学影像行业的物理学家来糊口。我的工作专长集中在解决问题和算法开发。为此，我广泛地使用了Matlab，主要用于信号和图像处理。另外，我得到了几个主要的工程方法学的认证，包括 MEDIC 六西格玛绿带、试验设计以及统计工程学。
|
||||
|
||||
我也写过书，包括《Linux 上的高幻想和技术工作》和《相互包容》。
|
||||
|
||||
请参阅我的完整开源项目，出版物和专利列表，只需向下滚动。
|
||||
|
||||
有关我的奖项、提名和 IT 相关认证的完整列表，请进行跳转。
|
||||
|
||||
|
||||
-------------
|
||||
|
||||
|
||||
via: http://www.dedoimedo.com/computers/fedora-25-wayland-vs-xorg.html
|
||||
|
||||
作者：[Igor Ljubuncic][a]
|
||||
译者：[cycoe](https://github.com/cycoe)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://www.dedoimedo.com/faq.html
|
||||
|
||||
[1]:http://www.dedoimedo.com/computers/fedora-25-gnome.html
|
||||
[2]:https://commons.wikimedia.org/wiki/File:DragonCon-AlienVsPredator.jpg
|
||||
[3]:https://creativecommons.org/licenses/by-sa/3.0/deed.en
|
||||
[4]:https://wayland.freedesktop.org/faq.html
|
||||
[5]:https://wiki.gnome.org/Initiatives/Wayland/Applications
|
||||
[6]:https://devtalk.nvidia.com/default/topic/925605/linux/nvidia-364-12-release-vulkan-glvnd-drm-kms-and-eglstreams/
|
||||
[7]:http://www.dedoimedo.com/computers/fedora-24-gnome.html
|
||||
[8]:http://www.dedoimedo.com/computers/lenovo-g50-distros-second-round.html
|
||||
[9]:http://www.ocsmag.com/2016/10/19/systemd-progress-through-complexity/
|
||||
Loading…
Reference in New Issue
Block a user