Because if you have network transparency in the display system then all your applications get network transparency for the display for free.
FTFY. You don't get transparent access to local files, or audio, or many other things that applications tend to want to do with the user's local environment.
I'm using Ubuntu because 1) Redhat basically abandoned the desktop,
Hmph, I'm using GNOME 3 on Fedora and it works OK, not worse than on Ubuntu at any rate. They have even added MATE into the distro for those who are outraged about GNOME 3.
The irony of this is, Motif applications (not to speak of anything more graphically intensive) were awful crap to work with over a slow/high-latency network connection.
The only legitimate modern use case I can imagine for using X11 over the network is running server administration software. Even this is suspect: WTF do you use that can't be controlled with command line tools, editing text files, or a web interface? The latter is far more realistic to find for modern software than graphical admin tools using X11. If you can't even easily transfer files in-protocol, it loses to web (and SSH) as a remote UI.
What's wrong with Upstart? Doesn't it restart services like it's supposed to?
It does, and it does other things, but it did not offer the flexibility and the features that systemd was able to provide (in less development time, too).
And here's a pattern: Canonical invests in a "better mouse trap", but they lack the first-rate talent it takes to create the kind of outstanding technology that other players would want to adopt, and their project is eventually passed over for something that works clearly better, enjoys greater mind share, etc.
I'm almost inclined to cut Canonical some slack here. Almost. I don't think NIH is such a horrible thing if the project in question still isn't anywhere near usable. In a situation like this, it's entirely possible that a team of paid, full time, competent programmers could start over from scratch and quickly surpass the original project. Given equal talent and effort, the Cathedral is always more efficient better than the Bazaar.
This is showcased nicely by the previous projects near-single-handedly developed by Canonical: Bazaar (heh; there were actually two iterations of it, both ultimately crap) and Upstart. Interestingly, neither of those was clearly NIH-motivated, they just were not satisfactory from the engineering standpoint as later, better projects have demonstrated.
OK, it was incredibly hard to dig it out from an obscure document confusingly called the FAQ:
Q: What is the drawing API?
A: "Whatever you want it to be, honey". Wayland doesn't render on behalf of the clients, it expects the clients to use whatever means they prefer to render into a shareable buffer. When the client is, it informs the Wayland server of the new contents. The current test clients use either cairo software rendering, cairo on OpenGL or hardware accelerated OpenGL directly. As long as you have a userspace driver library that will let you render into a sharable buffer, you're good to go.
How about waiting until it has proved it works and has advantages first. While a dumb framebuffer can theoretically perform better than something with a few layers of abstraction it hasn't done so yet, especially since some of those layers of abstraction in X are quite lean.
If you think Wayland is "a dumb framebuffer", you should educate yourself.
And there goes your troll moderation for insulting the One True Platform and its Creator.
Slashdot is getting ridiculous. Search for Windows Phone stories: notice any positive news reported elsewhere recently? Market share growing everywhere? Affordable Lumias giving cheapo Android phones the run for their money? Spotify getting their act together? No, but when one manufacturer decides they are not interested, stop the presses.
Well said, sir. I started to exclude Slashdot from my regular browsing routine because of all the dumb shit going on here recently (like articles written by incompetents about NoSQL solutions they don't understand the purpose of), but comments like yours make me reconsider.
And don't get me started when you combine javascript with the DOM interactions that are still, to this day, largely a mess and in critical areas, undocumented. Take that times 5+ browser variations (and IE being the worst offender), Javascript in the browser sucks!
I'd like to introduce you to jQuery. They really took care of all the mess for you.
This is Samsung we are talking about. I've sworn to never buy anything more complex than a microwave oven from Samsung again, after my TV which starts glitching wildly if the UI language is switched to one of the less-used languages available, and does something special to crappify the digital TV picture scaling, as compared to my set-top box.
I also have a Samsung branded Blu-Ray drive which works well, but probably only because it's made by a joint venture with Toshiba.
Which funnily enough is about right. The aircraft was a hack, a case of fix-what-we-have. The development history of the Spitfire is one of constant attempts to keep-up with the state-of-the-art as set by Germany and, to a lesser degree, the USA.
That's true of all designs that had been around when the war started. Messerschmitt Bf 109 was progressively souped up to the flaming hot rods that the G models were.
Constantly out-performed, out-manoeuvred and over-rated; the only reason the RAF continued to fly Spitfires is that there weren't enough Lend-Lease aircraft from the USA to meet demand.
Interestingly, the P-51 was designed to the British order, and first shipped to RAF. They found the early variants lacking, or at least not providing enough added value above Spitfires.
That makes perfect sense for a reasonable chunk of Android and even some iPhone users, but the userbase for Windows Mobile 8 phones is really small, and I doubt the people with the technical sophistication to download a model and print it at even a walk-in 3D place are Windows Mobile 8 users.
True, we all breathe through our mouths and haven't been known to download stuff off the intarwebs.
Slashdot Mirror
Because if you have network transparency in the display system then all your applications get network transparency for the display for free.
FTFY. You don't get transparent access to local files, or audio, or many other things that applications tend to want to do with the user's local environment.
Web interfaces are nothing compared to real GUI control elements.
Try to upload a file from your local machine into a forwarded X11 application, then come back to talk.
In other news, white smoke has been observed rising from Google HQ.
I'm using Ubuntu because 1) Redhat basically abandoned the desktop,
Hmph, I'm using GNOME 3 on Fedora and it works OK, not worse than on Ubuntu at any rate. They have even added MATE into the distro for those who are outraged about GNOME 3.
The irony of this is, Motif applications (not to speak of anything more graphically intensive) were awful crap to work with over a slow/high-latency network connection.
The only legitimate modern use case I can imagine for using X11 over the network is running server administration software. Even this is suspect: WTF do you use that can't be controlled with command line tools, editing text files, or a web interface? The latter is far more realistic to find for modern software than graphical admin tools using X11. If you can't even easily transfer files in-protocol, it loses to web (and SSH) as a remote UI.
What's wrong with Upstart? Doesn't it restart services like it's supposed to?
It does, and it does other things, but it did not offer the flexibility and the features that systemd was able to provide (in less development time, too).
And here's a pattern: Canonical invests in a "better mouse trap", but they lack the first-rate talent it takes to create the kind of outstanding technology that other players would want to adopt, and their project is eventually passed over for something that works clearly better, enjoys greater mind share, etc.
I'm almost inclined to cut Canonical some slack here. Almost. I don't think NIH is such a horrible thing if the project in question still isn't anywhere near usable. In a situation like this, it's entirely possible that a team of paid, full time, competent programmers could start over from scratch and quickly surpass the original project. Given equal talent and effort, the Cathedral is always more efficient better than the Bazaar.
This is showcased nicely by the previous projects near-single-handedly developed by Canonical: Bazaar (heh; there were actually two iterations of it, both ultimately crap) and Upstart. Interestingly, neither of those was clearly NIH-motivated, they just were not satisfactory from the engineering standpoint as later, better projects have demonstrated.
OK, it was incredibly hard to dig it out from an obscure document confusingly called the FAQ:
Wayland is of course a way to dump images on a dumb framebuffer
No, it's not. Please educate yourself.
How about waiting until it has proved it works and has advantages first. While a dumb framebuffer can theoretically perform better than something with a few layers of abstraction it hasn't done so yet, especially since some of those layers of abstraction in X are quite lean.
If you think Wayland is "a dumb framebuffer", you should educate yourself.
That's not true, they're not entirely generous to Chinese or Romanian ones either.
There was at least one episode where Clarkson praised a no-frills Dacia, saying that it would make great sense to sell this car in the UK.
And there goes your troll moderation for insulting the One True Platform and its Creator.
Slashdot is getting ridiculous. Search for Windows Phone stories: notice any positive news reported elsewhere recently? Market share growing everywhere? Affordable Lumias giving cheapo Android phones the run for their money? Spotify getting their act together? No, but when one manufacturer decides they are not interested, stop the presses.
Well said, sir. I started to exclude Slashdot from my regular browsing routine because of all the dumb shit going on here recently (like articles written by incompetents about NoSQL solutions they don't understand the purpose of), but comments like yours make me reconsider.
A more practical link for the less paranoid of us.
All I care about is whether it still runs Norton Commander.
You can keep your Start menu, god damned novelty seekers.
+1 to the list of pitfalls: "Can't create browser-agnostic websites".
Come on, IE 10 is pretty standards-compliant, even the mobile version.
And don't get me started when you combine javascript with the DOM interactions that are still, to this day, largely a mess and in critical areas, undocumented. Take that times 5+ browser variations (and IE being the worst offender), Javascript in the browser sucks!
I'd like to introduce you to jQuery. They really took care of all the mess for you.
This is Samsung we are talking about. I've sworn to never buy anything more complex than a microwave oven from Samsung again, after my TV which starts glitching wildly if the UI language is switched to one of the less-used languages available, and does something special to crappify the digital TV picture scaling, as compared to my set-top box.
I also have a Samsung branded Blu-Ray drive which works well, but probably only because it's made by a joint venture with Toshiba.
The win8 phones that I've seen are terrible. They are buggy, have weird behaviour, and a ghost town of an app store.
You must have seen some Windows Phone 8 devices that are very different from mine.
Who says the hardware won't ever be used in another device?
Detailed analysis of the "analysis".
But what did Nokia gain by going WP?
Support of a company that knows how to create and maintain a software platform.
Believe me, it was something that Nokia sorely lacked.
um not really, the successor the n9 sold more than their flagship much promoted "lumia 900"
I challenge you to provide a reliable source for this claim.
Which funnily enough is about right. The aircraft was a hack, a case of fix-what-we-have. The development history of the Spitfire is one of constant attempts to keep-up with the state-of-the-art as set by Germany and, to a lesser degree, the USA.
That's true of all designs that had been around when the war started. Messerschmitt Bf 109 was progressively souped up to the flaming hot rods that the G models were.
Constantly out-performed, out-manoeuvred and over-rated; the only reason the RAF continued to fly Spitfires is that there weren't enough Lend-Lease aircraft from the USA to meet demand.
Interestingly, the P-51 was designed to the British order, and first shipped to RAF. They found the early variants lacking, or at least not providing enough added value above Spitfires.
That makes perfect sense for a reasonable chunk of Android and even some iPhone users, but the userbase for Windows Mobile 8 phones is really small, and I doubt the people with the technical sophistication to download a model and print it at even a walk-in 3D place are Windows Mobile 8 users.
True, we all breathe through our mouths and haven't been known to download stuff off the intarwebs.