yeah, i went to turbo vision and TWindow stuff for 16 bit win3.1 gui ... tried delphi but never used it very much. Did some stuff with visual C++ and MFC ... today i do mostly python for my hobby project.

And so i started, a bit with batch-scripts, qbasic, VBA, until a friendly neighbor gave me 11 floppies with borland pascal and 10 kg of books. Then the real fun started with sound() and unit graph :).

> They tend to just watch.
[citation needed]

This is just not true. On "Nerd conventions", there is more intervention than on most other events, because nerds do not like people being asshats. Sometimes they are even to strict to people, who do not contribute enough. They may look down on you, if you do not contribute to oss community, but make closed source programs. Now imagine someone being a real asshole, like molesting some woman at the convention, (s)he will have no friends there instantly. Nerd culture is a culture, which strongly enforces an positive attitude.

Make it short: You cannot blame someone, because you changed your mind anytime later.

Is an insult to everyone, who was raped. Like real rape.

jep, thats okay. But i think a thick client is more suitable for many tasks, especially where the server part runs as privilgeded user.

i speak about a client-server model of having the gui here, and the server doing the work there, not about having the compositor here and the gui there.

for example have a look at mysql-workbench. You have a nice gui. on your pc. It connects via tcp or tcp-via-ssh to your server, where the db is running. nobody wants to have this program running on the server, forwarded via X11, rdp, NX or VNC.

so, mysql has the client-server model? What about having something like this for R and the display of its charts?

shouldn't such tools have some kind of client-server model?

> Have fun watching YouTube in Lynx.
Have fun with youtube via x-forwarding.

wayland is just the way to go. You see, that they are taking it serious.
They made a concept, they made a reference implementation, they are still calling it alpha, they are waiting for the toolkits and main desktops, they are reacting to feedback, they are looking at the distros and graphic card vendors.
It seems the concept was well thought from scratch instead of building on X11, clean and without old cruft.

So i guess wayland is like IPv6. Incompatible for a good reason, but using the fact that its incompatible anyway to implement stuff which would be impossible to add to X11.
And like IPv6, the transition is not easy, but i guess the compatiblity layers are easier to do.

some simple thought: Do you think slashdotters here are the only ones thinking about "X Forwarding" for wayland?

I guess they know its easy to do and best to be done, when the other stuff is api-stable and maybe working stable as well ;).

Maybe they are right, because they are not circumventing DRM.

But they are wrong with the idea of DRM. If you copy a DVD to harddisk with intact DRM and then play it, you can copy the harddisk and play the copy, too. So its circumventing DRM while keeping the DRM(-System) intact.

one word: realnames

> As soon as you send one-to-many e-mails (newsletter, mailing-list, announcement, or just corresponding with lots of friends) this starts to be a problem, as you need to recalculate a new hash for all mail recipient.
This is a plus.

If you have a legitimate use for such an amount of recipients, it will be worth the computing power. If not, it will stop your silly newsletter i do not want to receive anyway.

ftp://ftp.mozilla.org/pub/fire...