Right because rooting android and editing a text file or simply spending $4 is so much easier than installing CM.

Something has been validatedvalidated in this thread that's for sure.

You haven't met any real audio engineers have you. I don't even think Dr.Dre would use Beats headphones when preparing the final track for release.

That's funny. I don't remember taking a hearing aid to a concert so I could turn up the bass on live music. Flat response is what I want my speakers to produce. If bass is what was supposed to come out of a song, then the producer / engineer should have taken care of that at the mixing desk.

Yeah. ... If only there were developers working on other window systems to make them less wishful thinking. Oh well.

Or just wait.

I mean it's not like there aren't 100000 people out there with your exact complaints. Surely at least one person out there is a programmer who could actually publish the result of his work for others to use.

Ok I'm being slightly facetious. But the reality is the Wayland crew have demonstrated both VNC style remote rendering, and RDP style remote rendering and there was even some example code in Weston to do it. No one is asking you to switch to Wayland, but given how wide spread the ability to remotely run applications from a command line using an environment variable is, my view is that this is a problem which will be solved by someone given how the underlying protocol doesn't actually do anything to prevent it.

The way I have watched Linux evolve over the last 20 years has made me realise that even though I can't code and this open source thing is quietly useless to me, the problems do get solved when I'm not the only one out there experiencing them.

Now re-guess how many applications would adopt it in the name of smoother faster and (I'll admit this will creep in) shinier UI animations if it didn't break something in the process?

The fact that most of the X-window system isn't hardware accelerated is really nothing to be very proud of. In any case it's not the job of the application, it's the job of the toolkit or framework to do that.

X's only current saving grace is the slow development of Wayland. It seems producers of window managers are falling over themselves to implement Wayland support despite the general consensus that it's not actually production ready.

X is far from perfect. But unlike a lot of other "standards" which are far from perfect, only application support is what is holding X up as the default Linux distro of choice. If I had this discussion with you 10 years ago I would have used Xfree86 as the example package that is standard in all Linux distros. Yet after the X.Org fork and the code cleanup removing some 100000 lines of unused code everyone couldn't start using X.Org fast enough.

And yet I really enjoy working with mine. Granted I wouldn't be able to live without the mouse and keyboard, but a touch-screen augments it really nicely.

Vanilla Android most definitely does support USB OTG and I use a Nexus 7 with USB based telemetry for my quad copter. By default out of the box it won't automount USB devices, but there are two options. Either buy an app that sits and waits for a USB Mass Storage device which will automount it, or root the device with the instructions on Google's own website (rooting a Nexus device is perfectly legit) and follow some video guides on setting it up to automount.

That makes no sense what so ever. Tell me again how USB Mass Storage is magically different from the myriad of devices out there which have SD cards?
Also the Nexus 7 2012 has supported USB Mass Storage from the beginning. It mounts in /etc/usb. But you can't move apps to it. You can however move apps to external SD cards on devices which have support for them.

The 2012 Nexus 7 supports usb mass storage and has supported it even with the original version of Android shipped.

No it doesn't. Cost is only one small part of the entire financing equation. Financial risk includes the possibility of it all going horribly wrong as well. If it's 3 times more expensive, 10 times less likely to cause a never ending picket-line outside the fence, and 30 times less chance of catastrophe, then it may very well get the CAPEX approval required.

In other news the local large industrial plant I work at has spend over $100m in the last 2 years just on firefighting infrastructure. Probably closer to $300m over the last 5 years. All of this investment did not cause a single extra drop of product to get manufactured, yet it was both required by and paid for by our parent company.

Catastrophic failure of a hydroelectric dam displacing millions of people and killing hundreds of thousands is not correlation, it is direct causation.

Funny how a cement containment of a nuclear reactor leaking causes people here to freak out, but a cement containment of a hydroelectric dam collapsing is suddenly given a free pass.

Plugging your ears and singing la la la is not the same as waiting to get a full picture before making an informed decision.

But feel free to keep freaking the hell out, because ... fuck Poettering I guess?

I know you're talking in the literal sense, but the reality is that there's only one package providing the feature Gnome wanted.

My point was that Gnome does not have a dependency on systemd as the system management package. You are correct it has a dependency on logind. Why? Well why don't we ask the Gnome developers, and if they have a good reason for wanting a specific feature then implement it as a separate API. I remember reading there's at least one project looking to fork logind in a way to make it independent from systemd for this very reason, can't remember the details but it was in some slashdot post.

Now the irony is every time we discuss closed source we get endless comments about open source being better because you can change things the way you want. Now we're discussing open source there are are pathetically few people coming forward with this as a possible option.

Gnome does not have a dependency on a specific init system. It has a dependency on a specific feature of a package which people incorrectly refer to as only an init system. Find out what that feature is and implement it separately.