Originally posted by Awesomeness
View Post
Announcement
Collapse
No announcement yet.
GNOME & Intel Developers Plan The Wayland Future
Collapse
X
-
-
Originally posted by Honton View PostLooking at those claims made in the links confirms that Gnome did what was right. Saying no is not NIH, if what is offered is wrong or bad. Today Canonical's intentions are completely exposed. They want to control as much as possible. Random specs tossed over the wall does not do it. No matter if it is for notifications or a display protocol. KDE got fooled last time, but they did not do it with MIR.
And please do carefully read your last link. Was systemd a wrong choice? I think it is quite evident that Gnome did what was right. Systemd proved to do everything that the alternatives never reached. Overall Gnome have shown a very good judgement.
Comment
-
Originally posted by Honton View PostToday it is quite evident that Gstreamer was the right bet.
Gstreamer devs originally supported this approach, but later changed their mind and said it was a bad idea, refusing to provide the support for it they had earlier promised.
I also you completely ignored the part about dbus. I mentioned a bunch of other examples earlier in the thread but still haven't gotten a response to any of them.
Comment
-
Originally posted by TheBlackCat View PostGstreamer never was and never can be the right bet. KDE has an ABI compatibility guarantee. They could not use gstreamer directly because it was going to, and did, break API (not to mention ABI) multiple times during the KDE SC 4 cycle. Phonon is a way to cover over these API breaks so applications don't have to deal with it. They would have to do this no matter what if they wanted to support gstreamer, and they had to make it flexible enough to support multiple APIs because it had to be able to support distros running multiple versions of gstreamer, and if they are going to go that route they might as well make it API agnostic, which is what they did.
I am asking not to imply that KDE is doing something wrong here, but rather curiosity from a software engineering POV.
Also, I think this discussion pretty much derailed a few pages ago since there is basically only talk about semantics and grasping of straws to prove some kind of point.
Comment
-
Originally posted by Honton View PostMaybe it is time for you to go all MIR? After all, the only difference between MIR and Qt is 15 years of social bribe. Contributor agreements are contributor agreements. And pigs are pigs. Allways.
Comment
-
Originally posted by kigurai View PostWhy is it that KDE hit these ABI/API problems in gstreamer (which I failed to find any reference to, maybe my Google-fu is weak) but GNOME doesn't?
I am asking not to imply that KDE is doing something wrong here, but rather curiosity from a software engineering POV.
Also, I think this discussion pretty much derailed a few pages ago since there is basically only talk about semantics and grasping of straws to prove some kind of point.
because gnome does constantly break stuff.
I also remember gnome betting everything on CORBA - which was too complex, bloated and unnecessary. Kde develeped dcop. You could do everything with dcop. Script any KDE application of your choice. Window placement. Everything. Want to change the mixer setting of one app with your phone via bluetooth? With dcop that was EASY.
Gnome of course was unable to accept something written by the KDE camp and pushed for dbus. KDE agreed to use dbus for KDE4. And that had to wade through molasses because gnome tried to make dbus as gnome-only and kde-unfriendly as possible.
And whoever wrote that gnome is a driving force behind wayland: please pull your head out of your behind.
Comment
-
Originally posted by Honton View PostYes that is true. KDE has to stay NIH because they refuse to do major releases or target what ever parallel-installable version of Gstreamer. Instead they added an abstraction and made the test matrix explode. More code, more testings, less quality and a destiny as grave as aRts. No wonder the prime phonon developer went for cross-dressing instead of cross-backend abstractions. I would do the same thing.
Unlike gstreamer.
Comment
-
Originally posted by Honton View PostYou seem to forget the legal agreement is no threat to Digia. All they need to do is making a yearly release. It is so easy they can do it with a cronjob. And what happens if they fail? After a three months notification time KDE can do a relicense for the free editon only on desktop linux. That is it. That is as weak as it gets. The agreement was not done to protect freedom, it was red herring tactics. And you Sir is dragging it. A pig is still a pig even if you add lip stick or "legal agreements".
Originally posted by Honton View PostMark Shuttleworth is greatly inspired by Qt. Getting people to sign contributor agreements AND praise you product is the ultimate goal. He just needs to learn about PR from Qt. Social bribing plus lock-in for MIR can get him the next Qt. All he needs is some fanboys who will defend the contributor agreements. Some one like you. Because that is how Qt and soon MIR roll.
Comment
-
Originally posted by energyman View Postbecause gnome does constantly break stuff.
I also remember gnome betting everything on CORBA - which was too complex, bloated and unnecessary. Kde develeped dcop. You could do everything with dcop. Script any KDE application of your choice. Window placement. Everything. Want to change the mixer setting of one app with your phone via bluetooth? With dcop that was EASY.
Gnome of course was unable to accept something written by the KDE camp and pushed for dbus. KDE agreed to use dbus for KDE4. And that had to wade through molasses because gnome tried to make dbus as gnome-only and kde-unfriendly as possible.
Comment
-
Originally posted by Honton View PostYou need to understand the whole gstreamer deal. KDE tried to do media support on aRts, and it failed. After that Gstreamer was proposed as a new crossdesktop attempt to solve the matter. KDE bailed and went NIHy. Instead KDE went for Phonon so they could use what ever media framework they wanted. Today it is quite evident that Gstreamer was the right bet. So all the Gstreamer fuzz could have been avoided if KDE made better choices in the past. Today Gstreamer is largely accepted in KDE.
Originally posted by Honton View PostThis is just yet another example of KDE making poor choices. So don't expect others to adapt to what ever they offer. There is no reason to hate Gstreamer, hate KDE's poor handling.
Comment
Comment