LWN.net's Journal
[Most Recent Entries]
[Calendar View]
Saturday, June 8th, 2013
| Time |
Event |
| 12:46a |
[$] Little things that matter in language design
The designers of a new programming language are probably most interested in
the big features — the things that just couldn't be done with whichever
language they are trying to escape from. So they are probably
thinking of the type system, the data model, the concurrency support,
the approach to polymorphism, or whatever it is that they feel will
affect the expressiveness of the language in the way they want. But there
are lots of little things to consider too, and guest author Neil Brown
looks at some of them in an article from next week's edition. | | 5:25p |
The Wayland Situation: Facts About X vs. Wayland (Phoronix) Over at Phoronix, Eric Griffith has attempted to set the record straight on X and Wayland, with assistance from X/Wayland developer Daniel Stone. He looks at the failings of X and the corresponding "fixings of Wayland", along with some misconceptions about the two and some generic advantages for Wayland. " 'X is Network Transparent.' Wrong. [It's] not. Core X and DRI-1 were network transparent. No one uses either one. Shared-Memory, DRI-2 and DRI-3000 are NOT network transparent, they do NOT work over the network. Modern day X comes down to synchronous, poorly done VNC. If it was poorly done, async, VNC then maybe we could make it work. But [it's] not. Xlib is synchronous (and the movement to XCB is a slow one) which makes networking a NIGHTMARE." |
|