Originally posted by Danny3
View Post
Just at some point, what happend to me was:
Being unhappy with QT, I was saying: It's full of bugs which nobody is trying to solve, it's old style c++ api. So I started to work on my own, and the first backend for my own framework ist wayland and using vulkan for drawing.
This brought me back to the ugly reality: Wayland has very bad documentation and it's c (not c++) [lib-wayland].
If you wand to use wayland directly [to make a wayland client, in my case a framework], you are force to all kind ugly programming [raw pointers, global variables], and it takes a lot of effort trying to create a modern c++ framework based on an ugly c-library. Being forced to use reinterpret_cast that often is not funny any more. WTF was the most used expression I had during my contact with wayland.
Vulkan is the future for Linux (see the performance difference compared to opengl on linux), but wayland is not providing (and I suspect they even don't plan to have) a direct way vulkan to do the drawing. You have to go around over egl.
I'm sorry to say it, but to me it seems also in the linux/open-source world there is some kind of domination of some groups are imposing their view.
The problem with c is, is that it is forcing you to use bad design, it's harder to maintain, easier to introduce bugs. If wayland (lib-wayland) would be based on c++11 (c++14) with a great design, it would have been a triviality for the users to write easy and less error-prone wayland clients and frameworks.
On the following link is a great article which makes it clearer why we have to stop to build on top of .........
cipri
Leave a comment: