Hawaii Desktop Stable Released, Powered By Qt 5.2 & Wayland 137
An anonymous reader writes "The Maui OS Project has made their first stable release of the Hawaii Desktop. Hawaii is still catching up with GNOME, Xfce, and KDE in terms of features, but it's written from scratch atop next-generation open-source technologies. In particular, Hawaii 0.2.0 is powered by the brand new Qt 5.2 tool-kit and runs natively on Wayland's Weston 1.3 compositor. Hawaii 0.2.0 carries all standard Linux desktop features but more advanced desktop functionality is planned while focusing around a Wayland design and eventually their own Green Island Compositor."
Re:"next generation" my ass! (Score:5, Interesting)
And why would I care? (Score:0, Interesting)
So, is this news?
They get it (Score:5, Interesting)
They have a main webpage with a clean design, and they explain what they do and why anyone in the target audience should care, without falling prey to corporate-speak. That alone bests more than 90% of previous desktop environments, yet is the bare minimum than any user-facing project should have. Plus, the FAQ and About pages actually explain their motivations rather than a few obscure technical details.
That "operating system, a suite of software that makes your computer run" made me shed tears of joy.
Re:Way behind! (Score:5, Interesting)
X works on my operating system.
Re:Network Transparency ... solved (Score:5, Interesting)
" You have no idea what "network transparency" really means."
No... you don't.
Me*: Network transparency means that applications can render graphics to a local terminal or over a network with zero changes in code path and zero need to know anything about the underlying rendering model. Therefore, any remotely modern version of X.org is by definition not network transparent since every since modern local rendering technique such as DRI and compositing is completely incompatible with the fallback socket-based path that is used for networking remote X programs. Consequently, modern X is not network transparent and people who can't understand that just because it is still possible to send X pixmaps over a network socket in a kludgy manner does not mean X is "transparent" should maybe do some research on how X actually works instead of hurling insults.
Modern X-remoting is effectively pushing pixmaps over a socket in an inefficient manner. It is fundamentally different than the modern composited rendering path that effectively bypasses 99.9% of the original X server and is where Wayland is going. Additionally, if X were so beautifully perfect at network transparency then using it over a WAN connection wouldn't be one of the leading causes of suicide in network administrators and proxies like NX would never have come into existence.
Where "Me" includes the X.org developers including Keith Packard BTW.
You: "I MADE PRETTY PICTURES GO OVAR INTARNETS!! DARR!! NETWORK TRANSPARENT! SINCE SOME TYPES OF RDP ONLY TRANSFER DESKTOPS NOT INVIDUAL WINDOWS RDP NOT NETWORK TRANSPARENT!! DAR!!! X DEVELOPERS ARE STOOPID AND DON'T KNOW ANYTHING ABOUT X!!! DAR!!"