Maybe they are using RIAA counting systems and it was really 8 impacts 250m years ago?...and the subsequent loss of album sales was due to piracy and nothing to do with the majority of life on Earth being wiped out!!
Does this remind anyoneelse of the Region codes on DVD? You know, the ones that stop we watching a DVD from another region in my DVD player. Unless I eject the DVD press 1234 on the remote, then enter the region code?
What will I need to press on my new HDTV recorder to ignore this 'bit'? Please can we urge the manufactures to adopt a standard on the 'secret' key sequences required deactivating this 'feature'?
Xlib implements the most basic functions, and every widget library uses it
True. But if there were a versions of, say, GTK for Fresco, PicoGUI, and JourneyOS then a GTK app would run on all of these without the need of any of them to support XLib.
In the same way that the Windows version of GTK does not need to Window to support XLib.
Is XLib compatibilty really an issue? How much software is written in native XLib these days? Isn't compatibility with the various widget sets what we really need in a X replacement?
Let me guess, this "do not call" list infringes on the tele-marketing companies right to ring you up at 1am to tell you about their great money saving offers?
Slashdot Mirror
Why not name the features after other characters played by Lisa Kudrow?
Maybe they are using RIAA counting systems and it was really 8 impacts 250m years ago? ...and the subsequent loss of album sales was due to piracy and nothing to do with the majority of life on Earth being wiped out!!
Does this remind anyoneelse of the Region codes on DVD? You know, the ones that stop we watching a DVD from another region in my DVD player. Unless I eject the DVD press 1234 on the remote, then enter the region code?
What will I need to press on my new HDTV recorder to ignore this 'bit'? Please can we urge the manufactures to adopt a standard on the 'secret' key sequences required deactivating this 'feature'?
True. But if there were a versions of, say, GTK for Fresco, PicoGUI, and JourneyOS then a GTK app would run on all of these without the need of any of them to support XLib.
In the same way that the Windows version of GTK does not need to Window to support XLib.
Is XLib compatibilty really an issue? How much software is written in native XLib these days? Isn't compatibility with the various widget sets what we really need in a X replacement?
Let me guess, this "do not call" list infringes on the tele-marketing companies right to ring you up at 1am to tell you about their great money saving offers?
Doesn't it make you glad to be in a country were your democratic views are stored in an unprotected Access Database!
If you've got a set of tools that might help here, my not make them available?