ติดตั้ง Steam
เข้าสู่ระบบ
|
ภาษา
简体中文 (จีนตัวย่อ)
繁體中文 (จีนตัวเต็ม)
日本語 (ญี่ปุ่น)
한국어 (เกาหลี)
български (บัลแกเรีย)
Čeština (เช็ก)
Dansk (เดนมาร์ก)
Deutsch (เยอรมัน)
English (อังกฤษ)
Español - España (สเปน)
Español - Latinoamérica (สเปน - ลาตินอเมริกา)
Ελληνικά (กรีก)
Français (ฝรั่งเศส)
Italiano (อิตาลี)
Bahasa Indonesia (อินโดนีเซีย)
Magyar (ฮังการี)
Nederlands (ดัตช์)
Norsk (นอร์เวย์)
Polski (โปแลนด์)
Português (โปรตุเกส - โปรตุเกส)
Português - Brasil (โปรตุเกส - บราซิล)
Română (โรมาเนีย)
Русский (รัสเซีย)
Suomi (ฟินแลนด์)
Svenska (สวีเดน)
Türkçe (ตุรกี)
Tiếng Việt (เวียดนาม)
Українська (ยูเครน)
รายงานปัญหาเกี่ยวกับการแปลภาษา
X is... well, X is just bad
After that IRC convo, it seems reasonable to think that Mir could support Wayland. Keep in mind, Wayland is simply a protocol. In fact, during development of Mir, they may expose some API or protocol changes that Wayland could mirror or could accept a patch for... that would allow Mir to be a backend for Wayland. Display server competition could be interesting. Or in this case, irrelevant.
If they both wind up supporting or being able to support Android drivers (which Wayland supported contends is possible), what's the worst that happens? We get a bad implementation in Mir? That sucks, hopefully Wayland gets traction with other distros.
My question is, why would everyone want to implement /another/ backend after everyone just spent... a pretty long time... adding support for Wayland?
Frankly, that's what I'd like to hear, what do GNOME, Qt folks think about this? I guess Canonical is supposedly going to do that work, it seems like they could spend that money far more wisely on just making Unity Next "the best damn compositor and environment ever (TM)" and that would be exciting. The only Qt desktop we have now is KDE, which is great in a lot of ways, and not in a lot of other ways. Razor-qt is cool, but I find it... lacking. Unity and HUD are really cool ideas, even if you don't like Unity, try out HUD. As a dev, it's beyond brilliant. Never hunt for a menu item, ever, ever, ever again.
Anyway, let's hope that the pressure on NVIDIA/AMD enables drivers that both Wayland/weston and Mir/Unity could utilize.
Huh? Are you saying the devs won't? Are you saying something in the protocol is fundamentally wrong? My thoughts were more or less validated as possible based on what Wayland is and what Mir could be extended to do. And vice-versa.
That's to say nothing about whether that will happen, or how hates who or whatever telephone-chained politics-schtuff is or isn't really going on. /shrug
You big problem to worry about will be wayland and how distro will or will not make the switch.
There may be a way for the steam to decet and apply the relative files for you or there may be 3 options, Mir x.org and wayland. Download the relative option
I think the Wayland devs were more annoyed by the FUD Ubuntu/Canonical were using as justifications to abandon Wayland for their in house project mir. It's Ubuntu's NIH syndrom at work. Also if you followed the IRC conversation, Ubuntu/Canonical really came across as ♥♥♥♥♥ and amateurs.
Mir is developed by a handful of Canonical n00bs who have no clue about display server stuff. They know so little about it that they even got their stuff they complained about with Wayland all wrong. Just look at their TODO list on Launchpad and they want to implement it by October this year. If anything they will release some clusterf*ck like Unity 11.04 that is even worse than X and not even remotely on par with Wayland in terms of features. And let's not forget that it is unlikely that both AMD and NVIDIA just start supporting something that looks like it's going to be Dead on Arrival anyway. Unless Canonical wants you to play with open source Intel and Radeon driver. You can't even ues Mir with open source nvidia drivers. Even if NVIDIA supports it AMD is so slow it will take them ages. This means they alienate half of the Linux Steam Community.
Ask yourself why there are 25 windows manager 6 desktop enviroments 8 login managers 7 shells probably 20 terminal emulators but only 1 display server and 1 kernel? Becuase 1. it isn't trivial to pull a display server of 2. fragmentation is bullsh*t on the lowest level where everyone rather has 1 good solution. To bad braindead developers at Canonical don't get that. It's just about being an Apple like control freak for them.
There is not one developer that doesn't work for Canonical that actually thinks Mir is a good idea. Mhh wonder why that's the case...