Originally posted by smitty3268
View Post
Announcement
Collapse
No announcement yet.
Wayland Demonstration At XDS 2010
Collapse
X
-
-
C++ is a very powerful language, which is a double edged sword. It's easy to do some very nice things, but it's also easy to complicate the code. It encourages some of the best and worst in coders, so you just have to be careful about what you allow and make sure all contributors follow the recommendations.
Back to Wayland - at the very least, it would allow you to run on top of the proprietary drivers without forcing you to switch to the OSS Gallium3D drivers.
Leave a comment:
-
Originally posted by sylware View PostOk good.
Now, what benefit a wayland backend will have compared to a libdrm/gallium3D/libxkb backend for GTK+/Clutter?
The benifit is that you don't have to run an X server any more and have a much simpler and more lightweight display server.
Leave a comment:
-
Originally posted by nanonyme View PostActually I recall the main reason to switch from C to C++ is that it reduces (or rather hides) a lot of the complexity. That very same full-blown object orientation is what supposedly makes it simpler.
Note, simpler to write projects in, not to write a compiler for.
Please! Stick to the wayland topic!
Leave a comment:
-
C++ is better for larger projects, although headers could simply do the same in C, right?
C would be much better for small projects and low level stuff like drivers and kernels.
But why the hate for C++? I've seen it and I don't think it's realy based on anything but some nonsense experience.
Leave a comment:
-
Actually I recall the main reason to switch from C to C++ is that it reduces (or rather hides) a lot of the complexity. That very same full-blown object orientation is what supposedly makes it simpler.
Note, simpler to write projects in, not to write a compiler for.
Leave a comment:
-
Originally posted by V!NCENT View PostMay I ask why C++ would be such a disaster? It doesn't always mean slower...
Not that I think C++ would be better suited than C in this case.
I repeat, it's a matter of choice of where you put the limits. And *I* do drive strongly towards simplification as much as it can (not simpler) of the software stack *as a whole*. An efficient kernel and an optimizing C compiler are already complex enough. If one day, we have a language which adds significant features while retaining the simplicity of the C language, let's start to write an efficient kernel. In the meantime, let's stick to C.
But we move away from the wayland benefit subject compare to libdrm/gallium3d/libxkb. As far as I understand it, wayland benefit would only be the network protocol. Any thoughts?
Leave a comment:
-
May I ask why C++ would be such a disaster? It doesn't always mean slower...
Not that I think C++ would be better suited than C in this case.
Leave a comment:
-
C++ is kludge, we all know it
Originally posted by Plombo View Post
Now, what benefit a wayland backend will have compared to a libdrm/gallium3D/libxkb backend for GTK+/Clutter?
Leave a comment:
-
Originally posted by gnufreex View PostThanks for explanation. So, it is safe to say that Wayland is what will become X12
Leave a comment:
Leave a comment: