LWN: Comments on "Wayland and Weston 1.2.0 released"

Wayland and Weston 1.2.0 released

zenaan — Fri, 19 Jul 2013 07:43:48 +0000

Dear fedTROLL,

> 1. Are you associated with the failed Gnome project or its developers?
Absolutely. This really is just the GNOME project (you really need to work on your capitalizations by the way) core-core, but it was politically incorrect to call it GNOME. And Miguel didn't want Metacity's reputation to be tarnished, and Linus was disturbed at just calling it
/lib/systemd/gnome*.so
So Wayland it is :/

> 2. Are you associtaed with the freakish Ubuntu/Unity/Mir project?
Looks like capitalizations are not your only challenge. It's associATed.
Actually we're not associATed with UbNiMir, but they're associated with us - they basically write the code for us. It's called OUTsourcing, you might have heard of that?
And BTW, it could be seen as inflammatory to call us freakish ... not sure on your intent here...

> 3. Are you computer scientists or clueless idiots writing code?
Definitely not computer scientists. We wouldn't have had to outsource the development otherwise. I really thought you would have picked up on that. There are public mailing lists y'know - they're available on this thing called the InterNET; you might have heard of it? Wikipedia has an article on i... oh...

Well, good luck then.

PS - don't worry about censorship for this one. I'll just let 'em slide for a week, hey? Don't tell anyone ...

Wayland and Weston 1.2.0 released

fedtroll — Fri, 19 Jul 2013 00:57:14 +0000

Wayland Developers:

Just 3 simple questions for your project:

1. Are you associated with the failed Gnome project or its developers?
2. Are you associtaed with the freakish Ubuntu/Unity/Mir project?
3. Are you computer scientists or clueless idiots writing code?

Be on subject with your answers, or you will be censored by the Lwn.net editor.

Wayland and Weston 1.2.0 released

rahvin — Wed, 17 Jul 2013 19:38:57 +0000

- Improved thread safety and relaxed thread-model assumptions in libwayland-client. One of the restrictions in the client side library was that we assume that the toolkit or application will provide a "main thread" which is responsible for reading events and distributing them to event queues for the other threads. We also assume that there will always only be one such thread. It turs out that this breaks in many cases, in particular, it clashes with the threading model of EGL. The client side event processing has been reworked to not make those assumptions.

Maybe it's just me but it's nice to see them post in the release notes that they made a terrible assumption and have now changed course after realizing they made terrible assumptions. I think putting things like this in the release notes is important because it provides better publicity for something that may prevent someone else from making the same mistake.

Wayland and Weston 1.2.0 released

Jonno — Wed, 17 Jul 2013 16:57:37 +0000

>Great! Just two questions:
>1) is it rootless
>2) does it support persistent sessions?
>If not, can they be included with mean provided by RDP?

I don't know about the current Weston server implementation, but the RDP protocol supports both, as does the reference server implementation (Remote Desktop Services; formerly known as Windows Terminal Server).

Wayland and Weston 1.2.0 released

VITTUIX-MAN — Wed, 17 Jul 2013 13:11:20 +0000

Great! Just two questions:

1) is it rootless
2) does it support persistent sessions?

If not, can they be included with mean provided by RDP?

Wayland and Weston 1.2.0 released

gerdesj — Tue, 16 Jul 2013 13:43:14 +0000

It would seem so: http://www.phoronix.com/scan.php?page=news_item&px=MT...

Now all you need is a front end

Wayland and Weston 1.2.0 released

bojan — Tue, 16 Jul 2013 00:06:31 +0000

What of RDP support in Weston? Is that usable now?