Announcement

Collapse
No announcement yet.

April Fools' Or Should Wayland Switch Away From Using C?

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

  • April Fools' Or Should Wayland Switch Away From Using C?

    Phoronix: April Fools' Or Should Wayland Switch Away From Using C?

    An independent developer wrote a message on the Wayland mailing list this weekend how Wayland should "move away from C." While Rust is all the fun these days to those looking towards a "safer" programming language, it was suggested Wayland be re-implemented in Haskell...

    http://www.phoronix.com/scan.php?pag...-Not-In-C-Talk

  • #2
    I feel that Wayland should be implemented in Amiga AMOS simply because it allows you to change the color of the cursor without much trouble.... yeah!....

    http://www.dirtcellar.net

    Comment


    • #3
      Haskell? I didn't expect that.

      Comment


      • #4
        Originally posted by waxhead View Post
        I feel that Wayland should be implemented in Amiga AMOS simply because it allows you to change the color of the cursor without much trouble.... yeah!....
        Code:
        Curs Pen 5
        Woo!

        Comment


        • #5
          Only on April 1st. debianxfce sounds normal

          Comment


          • #6
            This is like I do my c++17 gui framework. The wayland part I hide in a "unsafe class". It's very sad, that wayland is forcing me to use "reinterpet_cast", which is something like a little time-bomb. At least I found a way to put the unsafe stuff more tightly together instead of spreading it all over the framework.
            It means if something goes wrong (likes leaks and crashes) it will be because of the framework, and not because of the user of the framework.
            With c++ you can have the same speed (or faster!) and having at the same time more safety.

            The c example of wayland clients/servers could look in c++ easier to follow with less code, better structured....
            There is a good reason why you barely find applications based on wayland directly! Gnome and KDE are working since years on wayland support and it's still not ready. If lib-wayland would be done with c++14 and being well designed, writing wayland clients would be a triviality! It would be easier than using QT [since QT has old style c++ api].

            cipri

            Comment


            • #7
              the should use c++

              Comment


              • #8
                Finish the dam thing before rewriting it, april fools or not.

                Comment


                • #9
                  Originally posted by phoronix
                  Wayland in [your favorite language]
                  Ha ha. What if I told you my favorite language is ASM? I'm joking, I prefer C.

                  A skilled C developer runs his program with Valgrind, and admires absence of errors and memory leaks.

                  Comment


                  • #10
                    Originally posted by Xorg View Post
                    Ha ha. What if I told you my favorite language is ASM? I'm joking, I prefer C.

                    A skilled C developer runs his program with Valgrind, and admires absence of errors and memory leaks.
                    That's true. That's what consumes every C developer sooner or later. Documentation, API and developer friendly interfaces then get lost in the abyss. Along with general usability and quality.

                    As long as it is fast and memory efficient (because you wrote it of course; hello security issues) nothing else matters.

                    Comment

                    Working...
                    X