Sorry I misworded the second sentence - I meant the dinosaur in the article.

Multinationals use Ireland in the same way called the double Irish system. Ireland allows an Irish registered company to domicile in a tax haven (so it's tax liabilities might be in Bermuda). So multinationals establish 2 Irish companies. The first is legit and employs people and runs sales & services. This company charges other subsidiaries worldwide for its work so the tax liabilities move to Ireland. Then the first company pays the second a massive chunk of its revenues as royalties. Since the second company is domiciled in a tax haven there is no tax on these royalties and the multinational only pays tax on the remainder. And Ireland has low corporation tax for that part too.

There is supposedly a double Irish Dutch sandwich variant which presumably yields similar results. Apparently the loophole is being closed since most countries are getting so pissed off with tax avoidance / evasion that they're cooperating (or being coerced) into stamping it out.

Air braking, manoeuvrability & stabilization would be good uses. e.g. an ostrich can zig zag while running by sticking out its wings which might be useful if it's being chased by a predator or trying to catch prey.

Red Hat used to ship with Enlightenment (and employ its author) but dumped it for GNOME and Sawmill IIRC. Red Hat wanted a more conservative and familiar desktop experience and E wasn't delivering on that.

Weston has support for RDP. i.e. you establish a remote session to it via a RDP client and you see your apps. RDP has a seamless mode though I don't know if the compositor supports that although it could in theory.

It's a way for client applications to connect to a display, receive input events, and render into surfaces without using X11. The surfaces are rendered via a compositor which could push the result out to the screen or remotely. It's less complex, context switching and data duplication than X11 so it should be more efficient and yield a better desktop experience.

Wayland is a protocol for client apps to talk with a compositor. The compositor can offer remoting if it wants to and indeed Weston does.

So what they claw back from the CPU overhead of decoding MP3, they lose by hogging the IO and increased memory use (and paging). Sounds a pretty weak rationalisation really. Besides, if it really were an issue for dual core machines, then they could decode and cache the audio on those machines rather than inflicting this stupid overhead on every machine.

You just know that Apple will continue to use a proprietary connector. I also wouldn't be surprised if they concoct some bullshit reason to put a chip into the cable that hobbles charging unless you happen to use an Apple authorised charger.

Weston supports RDP in about 1000 lines of code hooked up to FreeRDP. So yes it does remoting and any other compositor can do it too.

Require mandatory vaccination. The only exemption being for children who cannot receive the vaccine for medical reasons. And if an unvaccinated child is subsequently harmed by contracting measles prosecute the parents for child endangerment.

My understanding is that mammoths are fairly conspicuous creatures, what with them being giant hairy elephants.

Not so much pixel scraping but pixel pushing. Most apps render themselves into a pixmap and push it around the network. They're not using X primitives. They *might* be using XRender primitives or they might not. It's still a large amount of data, and combined with the synchronous nature of X, it's horribly inefficient. A remoting enabled compositor for Wayland could probably work better than X, even for the one thing that people always go on about X being good for.

So enlighten us where I have gone wrong please. And for someone quick to call it "your pet topic", you sure as hell have quite the posting history about it yourself. It's called projection you know.

I don't see how portability is any better or worse for using Wayland than X. If I were to target a new graphics card or kernel with X then I'd have to port the code to that platform, e.g. write a new backend. X may be more accustomed to doing this but the work still has to be done. Why is this not the same for Wayland?

It may be that Wayland / Weston targets Linux in the first instance (just as Linux kernel originally targeted x86 processors) but that does not preclude it from other kernels over time. If someone were to try I suspect the problem would lie less in porting Wayland / Weston and more to do with the sorry state of GPU drivers for other kernels. In the meantime, use X. I doubt it's going away any time soon.