Announcement

Collapse
No announcement yet.

More Details On The OpenGL Situation In KDE's KWin

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #61
    Originally posted by V!NCENT View Post
    Well there's an algorithm for that:
    1. Pick your favorite: KDE or Gnome;
    2. Bash the other DE to get rid of your anger (For example: "Gnome doesn't have fallback, lol fscking FAIL DE" <- and you'd be right);
    3. Defend your DE from incomming critisism;
    4. Go back to step 2.

    What surprises me is that nobody from the key players mentions that steps will be undertaken to FIX this composting issue. So I wonder if it will be fixed or...

    Comment


    • #62
      Originally posted by yotambien View Post
      The Kwin developer himself stated that it's not a trivial task, taking him over 1 day to compile.
      Assumably he's compiling all of KDE but a normal user wouldn't need to. Then again, a normal user also wouldn't know how to strip down the build so they don't have to compile everything.

      Comment


      • #63
        Originally posted by TemplarGR View Post
        So what happens when a new user decides to finally give Linux a try and uses KDE? When things begin to segmentfault on him and desktop begins to crash, he will decide Linux is broken and move to Windows again. In effect, KDE's unstability gives Linux a bad name, and this is something that concerns all os us, KDE users or not...
        What happens when Gnome apps crash? Exactly the same I guess.

        So enough of justifying poor development practice just because we are fanbois of a project.

        KDE devs were wrong, and let's hope they will change their practices in the future...
        Is this a good practise when I have to bloat my system with mono, python, vala to have my Gnome apps working? What are good development practices in your opinion?

        Comment


        • #64
          Originally posted by kraftman View Post
          Is this a good practise when I have to bloat my system with mono, python, vala to have my Gnome apps working? What are good development practices in your opinion?
          If you're doing embedded, I understand the concern. Otherwise pretty much a useless concern, hard disk space costs about nothing these days.

          Comment


          • #65
            Originally posted by TemplarGR View Post
            My dbus is up-to-date, unlike KDE fanbois like you i use a real distro...ArchLinux.
            Then you're affected by dbus bug. It will be fixed in the next release afaik. I'm also using Arch and I'm not affected.

            Comment


            • #66
              Originally posted by sundown View Post
              What surprises me is that nobody from the key players mentions that steps will be undertaken to FIX this composting issue. So I wonder if it will be fixed or...
              I'm not a 'key player', but the problem is incomplete features and bugs being exposed. The graphics stack (ignoring GPU specific drivers) isn't done yet.

              It's a matter of time as people are simply making it all work. It's shiny, it's new. If you run the bleeding edge, then expect it to be sharp and bleedy

              Comment


              • #67
                Originally posted by nanonyme View Post
                If you're doing embedded, I understand the concern. Otherwise pretty much a useless concern, hard disk space costs about nothing these days.
                I like consistency and I try to keep my system clean. It makes me sick when I have to dowload some pile of junk just for a single application.

                Comment


                • #68
                  Though to be honest, it's perfectly possible to have a Gnome installation that doesn't need Mono.

                  Comment


                  • #69
                    It is sad when forum moderators delete posts just because some babies cry "troll" everytime someone disagrees with them.

                    I can understand it somewhat, it is easy for a flamewar to errupt, but sometimes people overreact.

                    Comment


                    • #70
                      Originally posted by kraftman View Post
                      What happens when Gnome apps crash? Exactly the same I guess.



                      Is this a good practise when I have to bloat my system with mono, python, vala to have my Gnome apps working? What are good development practices in your opinion?
                      1. It is a different thing an app crushing, and a different thing a window manager crushing...

                      2. If you believe KDE is less bloated, then you are wasting everyone's time here... Get back to school. BTW, having an additional set of libraries doesn't make a system bloated, but i won't waste my time trying to explain it to you.

                      Comment


                      • #71
                        I share the desire for a clean system. I install things that I use, and don't install things that I don't use. It saves me lots of trouble while managing the system and it is safer from exploits because you don't have lots of unneeded software running.

                        That said, I have GTK+, and all the needed additional libraries (such as Pango and friends) installed and don't mind them. It's an alternative toolkit, and a good one at that. If I have a choice, I'll usually go for the Qt/KDE program, but there are some fantastic apps which are GTK-based, and I use them happily (like GIMP and Inkscape, sometimes Gnumeric).

                        But what I don't want is hundreds of services running in parallel doing exactly the same thing. I don't need two message-passing frameworks (thank heavens for dbus!), I don't need three audio daemons, four desktop indexing daemons, two semantic tagging frameworks, three different personal information stores, and what not, each servicing a different application.

                        I only want ONE of each, as a sane desktop will only use ONE of each, and use them everywhere. This stuff will not get installed, and apps which depend on them will not get installed either. I like the KDE technologies in this respect (dbus, kioslaves, akonadi, etc.) and use them where I need to (desktop search+tagging is off, don't need that). Luckily, the GTK-based apps I use (like Inkscape and GIMP) don't really depend on any of that stuff.

                        Comment


                        • #72
                          Originally posted by kraftman View Post
                          I like consistency and I try to keep my system clean. It makes me sick when I have to dowload some pile of junk just for a single application.
                          Nice. Why don't you say that to Mono, Python, Vala developers, that all their products are just junk?

                          Not every tool is suitable for every application, and besides, each developer is accustomed to specific tools and having a big set to choose lowers the difficulty to contribute. A small part of HDD is a small price to pay for that.

                          You are seriously so much ignorant that you are bordeline trollish, and i am the one that had a post deleted...

                          Comment


                          • #73
                            Originally posted by pingufunkybeat View Post
                            I share the desire for a clean system. I install things that I use, and don't install things that I don't use. It saves me lots of trouble while managing the system and it is safer from exploits because you don't have lots of unneeded software running.

                            That said, I have GTK+, and all the needed additional libraries (such as Pango and friends) installed and don't mind them. It's an alternative toolkit, and a good one at that. If I have a choice, I'll usually go for the Qt/KDE program, but there are some fantastic apps which are GTK-based, and I use them happily (like GIMP and Inkscape, sometimes Gnumeric).

                            But what I don't want is hundreds of services running in parallel doing exactly the same thing. I don't need two message-passing frameworks (thank heavens for dbus!), I don't need three audio daemons, four desktop indexing daemons, two semantic tagging frameworks, three different personal information stores, and what not, each servicing a different application.

                            I only want ONE of each, as a sane desktop will only use ONE of each, and use them everywhere. This stuff will not get installed, and apps which depend on them will not get installed either. I like the KDE technologies in this respect (dbus, kioslaves, akonadi, etc.) and use them where I need to (desktop search+tagging is off, don't need that). Luckily, the GTK-based apps I use (like Inkscape and GIMP) don't really depend on any of that stuff.
                            Pal, your level of knowledge is so low that i no longer wonder why you support KDE...

                            Just because you have software installed, doesn't mean it is *running*, or listening to requests.

                            And just because you have another desktop environment installed, doesn't mean its processes are running when you are using *another* desktop envrionment...

                            For God's sake, learn some stuff before you write...

                            Comment


                            • #74
                              Templar, stop trolling.

                              It's incredible what this thread has turned into. The situation is quite simple, really:

                              - Mesa advertises features that are known to be broken. The driver guys should think about this
                              - The communication between the KWin team and the Mesa team was not really good in this case. All the devs should think about this instead of pointing fingers.

                              I mean, it's obvious that someone would march in here with a prepared "KDE=SATAN!" diatribe, but it's just a friggin optional eye-candy plugin, and you have to manually disable the blacklist to even run it.

                              Comment


                              • #75
                                Originally posted by TemplarGR View Post
                                1. It is a different thing an app crushing, and a different thing a window manager crushing...

                                2. If you believe KDE is less bloated, then you are wasting everyone's time here... Get back to school. BTW, having an additional set of libraries doesn't make a system bloated, but i won't waste my time trying to explain it to you.
                                Compiz is crashing sometimes too. I didn't saw Metacity or Kwin (without compositions) crashing. If you would be so kind and explain this I'd be thankfull. However, I really believe KDE is much less bloated. I don't like the idea - python everywhere. KDE apps share libraries and I'm not so sure about this when comes to Gnome.

                                Comment

                                Working...
                                X