Announcement

Collapse
No announcement yet.

KWinFT Projects Hit Beta Ahead Of Stable Releases Aligned With KDE Plasma 5.20

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

  • #21
    Originally posted by 144Hz View Post
    tildearrow I’m cheering any de-cute effort.
    De-cute-ing should be the main focus for KDE in their next version. The more they depend on Qt, the easier is it for the greedy Qt company to pressurize them into making changes to this already very weak contract that are purely in the favour of the Qt company.


    But the actual sad story is that the GPL failed to protect freedom here. It relies too heavy on the idea that a re-licensing is nearly impossible if multiple people own the code in one project. But as the Qt company only accepts contributions if the owner gives full rights to the Qt company, and the KDE people being fully happy with that creates the situation where the Qt company is not just able to re-license community contributed code under their greedy proprietary license but also be in the position that it can stop releasing GPL versions. KDE e.v. could then re-license what was GPL to whatever they like but would be cut off from all the progress made after that.

    It was a bad idea to stick with Qt after the 4 years of them refusing to even consider the GPL. Back then would have been the best chance to switch to a FLOSS and better tool kit what would be harder but is still 100% necessary today.

    Comment


    • #22
      Originally posted by Alexmitter View Post

      De-cute-ing should be the main focus for KDE in their next version. The more they depend on Qt, the easier is it for the greedy Qt company to pressurize them into making changes to this already very weak contract that are purely in the favour of the Qt company.


      But the actual sad story is that the GPL failed to protect freedom here. It relies too heavy on the idea that a re-licensing is nearly impossible if multiple people own the code in one project. But as the Qt company only accepts contributions if the owner gives full rights to the Qt company, and the KDE people being fully happy with that creates the situation where the Qt company is not just able to re-license community contributed code under their greedy proprietary license but also be in the position that it can stop releasing GPL versions. KDE e.v. could then re-license what was GPL to whatever they like but would be cut off from all the progress made after that.

      It was a bad idea to stick with Qt after the 4 years of them refusing to even consider the GPL. Back then would have been the best chance to switch to a FLOSS and better tool kit what would be harder but is still 100% necessary today.
      Yeah, sure, that makes perfect sense.
      But why stopping at Kde? There are many other projects that need True Freedom™!
      Let's rewrite everything written in Qt with a better and truly free toolkit!
      Do you have any suggestions?

      Comment


      • #23
        Originally posted by JackLilhammers View Post

        Yeah, sure, that makes perfect sense.
        But why stopping at Kde? There are many other projects that need True Freedom™!
        Let's rewrite everything written in Qt with a better and truly free toolkit!
        Do you have any suggestions?
        https://www.copperspice.com/
        https://www.copperspice.com/docs/cs_.../timeline.html

        Comment


        • #24
          KDE developers BTFO!

          Comment


          • #25
            I tried to use it because it's interesting, but Qt seems easier and cleaner.
            Also CopperSpice has no python bindings

            Comment


            • #26
              Originally posted by JackLilhammers View Post

              Yeah, sure, that makes perfect sense.
              But why stopping at Kde? There are many other projects that need True Freedom™!
              Let's rewrite everything written in Qt with a better and truly free toolkit!
              Do you have any suggestions?
              Did you just ignore a legitimate concern to make a stupid, unfunny joke? Qt is very much in power to lock KDE out whenever they want. Might be just a matter of time.

              Comment


              • #27
                Originally posted by angrypie View Post

                Did you just ignore a legitimate concern to make a stupid, unfunny joke? Qt is very much in power to lock KDE out whenever they want. Might be just a matter of time.
                How would Qt do that with the source code readily available and GPL licensed?

                Comment


                • #28
                  Originally posted by angrypie View Post

                  Did you just ignore a legitimate concern to make a stupid, unfunny joke? Qt is very much in power to lock KDE out whenever they want. Might be just a matter of time.
                  I think I might have.
                  It's been a matter of time for 24 years.
                  Based on this I'm legitimately not very concerned.

                  PS: That doesn't mean ignoring some manager's bad ideas, but I'm not worried about Kde. At all
                  PPS: This reminds me of the whole paranoia around .Net, Mono, and C#.
                  Spoiler alert, Mono was not a trap, .Net Core is open source and will become the only .Net, and C# is awesome

                  Comment


                  • #29
                    Originally posted by carewolf View Post

                    Branched out? It is where it started! It is older than C++98
                    I know, but today we do have modern C++. So I'd avoid using Qt when they intersect. As above, in my opinion Qt is fine for a GUI toolkit, but not when it's used for libstdc++ replacement today which is what Roman pointed out in the past was one of the issues.
                    Last edited by shmerl; 09-28-2020, 08:14 PM.

                    Comment


                    • #30
                      Originally posted by bug77 View Post

                      How would Qt do that with the source code readily available and GPL licensed?
                      By shifting the burden of maintaining the toolkit to the KDE team? Maybe some lawsuits for good measure.

                      They don't need to forcibly kick them out and slam the door. Microsoft has killed competitors indirectly since forever and it worked wonders for them.

                      Comment

                      Working...
                      X