Linked by Thom Holwerda on Sun 12th Feb 2012 23:23 UTC
Gnome "One of the things that the GNOME design crew have been focusing on recently is creating a new approach to application design for GNOME 3. We want GNOME applications to be thoroughly modern, and we want them to be attractive and a delight to use. That means that we have to do application design differently to how we've done it in the past."
Permalink for comment 506927
To read all comments associated with this story, please click here.
mcpatnaik
Member since:
2011-09-02

I really don't dislike Wayland. It skips one of my use-cases, That is remote desktop. I have been using remote rendering of X since long and with satisfaction. If tomorrow OpenSUSE defaults exclusively to Wayland (That's our pet distro) or KDE switches to it, I am in serious trouble if remoting code does not come to Wayland before the switch.
See Wayland faq http://wayland.freedesktop.org/faq.html

Is Wayland network transparent / does it support remote rendering?

No, that is outside the scope of Wayland.

My point of view is that every software project repeats a design cycle. But to adopt a new strategy even before you finish the previous goal is not professional. Goals for an iteration should be complete before you switch on to a new structure. Just don't leave users midway because you got a fancy for a new architecture.
Porting is really painful. Many good apps get lost in the switch. We don't have an army of developers fed by big money and directed by corporate vision. In OSS world we create software for ourselves. The end user is just like a family member. Let's think from his point of view. Backward compatibility is a necessary evil. If devs switch to every new and promising architecture and the old falls out of the ecosystem eventually, the community is at a loss. It is a social responsibility.

New technology and re-engineering doesn't always means that the end result will be less stable, or that the system will be "unstable". Quite the contrary, specially when it comes to software development and new developments.

Not every new architecture brings robustness immediately. Search tracker-store and nepomuk using 100% cpu in google. Let's also see the bug status of popular projects (Libreoffice, KDE, Gnome). It needs a lot of time and testing to build robustness. What happens to the user till such time? he is left with a plethora of half baked software in the name of choice. will anyone care?

Reply Parent Score: 3