It's not very interesting to ask whether we should adopt both technologies at the same time, since that's already happening. The transition to IPv6 has been happening for many years, though far too slowly. The transition to DNSSEC just started recently.
The problems are only similar in that the value of adopting either IPv6 or DNSSEC is dependent on the number of other people doing the same. In other words, like most things on the Internet, it's all about network effects. However, the two problems are otherwise orthogonal. DNS (and therefore DNSSEC) is a protocol built on top of IPv4 and/or IPv6. Other than the ability to return either version of IP address, DNS doesn't care which version of IP it's used on.
Fortunately, unlike Lucas, Scott has continued to make a variety of good movies. He hasn't worked on one series his entire career. As long as the writers don't totally suck, these movies will be decent.
Also, misinformed != stupid. Incredibly, the Slashdot title is more accurate than TFA on that point. I would guess that some misinformed people watch Fox News and some are misinformed as a result of watching it. This produces a feedback loop.
To anyone who believes in a religion, your belief is just as nutty as theirs is to you. You seem to be saying that no one should believe in anything unless they agree with you. Your logic will be consistent as soon as you concede your opinion that all religions are "made up" is just as unfounded as the religions about which you claim this.
More importantly, the small amount of CGI in Tron was not intended to look photo-realistic, so it doesn't look dated. Yes, it's very simple by the standard of what can be done today, but the entire look of the world (most of which was not CGI) was intentionally minimalist.
I agree with this completely. I think it's pretty clear that climate change is happening and greenhouse gases released by burning hydrocarbons has a lot to do with it. Though there's plenty of consensus among scientists about that, there is far less about how quickly the climate will change, what the consequences of that will be, and what we should be doing about it.
So, how long will this dream last after the first lawsuit to protect some insect local to the area to be covered by solar panels?
Yes, it's not the USA, but the companies involved in the process will be first world companies, with all the potential for idiotic lawsuits implicit in first world sensibilities....
Japan may be "first world" but, is suing about imagined endangerment of species as common there as in the US? Keep in mind that Japanese people eat a lot of whale, when it's considered taboo almost everywhere else. Also, the Sahara expands constantly as a result of land mismanagement, so I'm sure there's plenty of habitat for both solar cells and insects.
Now all we have to do is build a massive worldwide network of new transmission lines, stabilize the governments of Africa, and get every country in the world to agree on how the power is to be shared.
Linux Mint will still use GNOME for the forseeable future.
By "still use" do you mean stick with GNOME 2 indefinitely or switch to GNOME 3? I haven't tried either Unity or GNOME Shell yet, but it seems pretty clear that they're both very different from a typical GNOME 2 desktop. I don't think it's fair to characterize Uubntu's switch to Unity as a major change for users in contrast with distributions that switch to GNOME 3.
Lucas didn't direct "Return of the Jedi" either: it was Richard Marquand. According to Lucas, he didn't have time to direct either episode 5 or 6. IMHO, those were the two best because Lucas didn't direct them as well as the fact that Lawrence Kasdan was involved in the writing. What Lucas doesn't explain is why he had time to write and direct the prequels by himself, as they seem to have been much bigger, more complex productions. It seems to me that when he realized his limitations and collaborated with better writers and directors, he obtained the best results, but when he decided he could do it all himself, things went downhill.
Are you implying that Apple owns all iPods, iPhones, and iPads, regardless of how many people think they've purchased them? I suspect that even the most unquestioning Apple fan would balk at the idea that he doesn't own his shiny device.
A very large number of Linux users rely on the proprietary drivers, and the open source drivers will never be as good.
That is a depressing attitude which could become a self-fulfilling prophecy. It's also irrational, as many Linux drivers are superior to their proprietary counterparts. If I believed it, I'd just settle for using OSX (or maybe even Windows) rather than trying to use a Free system. Why would you want to use a system that's always behind?
So, you're really saying that you can avoid a lot of hassle if you just stick to English and ignore all other languages. That has been the attitude of many programmers for decades, but it just isn't good enough any more.
Apple has not gotten it right. I am running several X11 apps on OSX right now and they are second class citizens. Apple has made it very clear that there's only one right way to do things (use their proprietary protocol and libraries) and they don't let you forget it when you run X11 apps. Also, various X11-based desktops have very similar capabilities to Aqua in desktop effects, so dumping X11 is clearly not necessary.
X11 never has and never will depend on TCP/IP. It only depends on some kind of reliable bi-directional byte stream. The common case is a local (Unix domain) socket in the file system, which is very efficient. In that common local case, further optimizations are routinely used via the shared memory X11 extension and graphically intense apps that do things such as play video or display OpenGL graphics usually use direct rendering, which doesn't go through the X11 protocol stream and therefore wouldn't be improved by a switch to Wayland. The proponents of Wayland contend that certain optimizations related to desktop compositing are difficult or impossible when using X11, which seems plausible, but I don't think it's clear that it offers a giant improvement in performance.
Assuming Wayland and the hardware get along, which requires modern Linux interfaces like KMS, and X.org as a Wayland client has full GLX functionality, it should have little effect. That would currently (probably indefinitely) exclude Nvidia proprietary drivers: just one more reason to dump them.
Choice of distribution is one of the great strengths of the GNU/Linux community and I wouldn't recommend Ubuntu for everyone, but it is still entirely possible to turn off Pulseaudio and configure libasound to use hardware devices directly, just as it's possible to use Pulseaudio on Slackware or Gentoo. Also, though Canonical did not transition to Pulseaudio carefully enough, I do think it was a good move overall. Hopefully if they decide to move to using Wayland by default, they will have learned from their mistakes in the Pulseaudio transition.
I also don't think OSX is a good example to follow as I'm using it right now and even on the same machine, X11 clients are second-class citizens. The way to avoid killing remote capability is to leave the X11 client in the widget libraries like Gtk+ and Qt and add the Wayland client, so that apps continue to work with either protocol. As much as Canonical may want it to happen, Gtk+ and Qt (and various other X11 widget libraries) will not suddenly transition to an entirely different protocol.
Apple, starting with the NextStep/OpenStep GUI libraries, had the choice to using an existing windowing system underneath (such as X11) but chose to write a brand new one and only later added X11 as an Aqua client. Canonical has a system based on X11 and wants to transition to a different protocol, but needs to support existing clients, so they shouldn't have an Apple-style attitude that every user and developer is captive to their whims.
I have also played around with Fresco and noticed that while there have been many claims that X11 needs to be replaced and a number of attempts to do so, it has not proven to be necessary and the attempts to replace it have fizzled. I don't know enough about the X11 protocol, the Wayland protocol, or the low level details of managing composition to evaluate how urgently X11 needs to be replaced, but it seems plausible that doing so could allow optimizations that are currently difficult to impossible. Smooth desktop effects on small and/or inexpensive hardware and simultaneous low power usage are great goals, but the need for a change as big as this needs to be well-justified.
In contrast to Fresco, Wayland is nowhere near as ambitious and therefore has a much greater chance of success IMHO. Like X11 and unlike Fresco, it doesn't attempt anything related to GUI policy, but concerns itself only with the low level display manipulation.
I'm sure that to provide adequate backward compatibility, Canonical will need to make sure X.org is available whenever a non-Wayland client needs it and those clients aren't second-class citizens. If they expect all currently used Widget libraries to be adapted to be Wayland clients, that's a huge mistake. It's similar to the transition to using Pulseaudio by default: when libasound clients worked as well as they did talking directly to hardware (which sadly was long after Pulseaudio was run by default), that took care of the majority of transition problems. Hopefully they've learned from their mistakes in that transition and will be more cautious and/or diligent next time.
Also, I'm pretty sure they'll need to allow selection of X.org instead of Wayland to talk directly to hardware on systems that don't have suitable graphics hardware.
X.org was never intended to be a "thin fast X11 replacement", but a fork of XFree which was more modular and easier to add new features to. Both X.org and XFree always have been and always will be X11 servers.
There are several small X11 servers, but Wayland isn't one of them (it is not an X11 server). In contrast with X.org, it actually requires the "super fancy graphics" features, which are present on most new graphics chips, whether on the motherboard or on a big card. X.org never has required anything fancy from the graphics hardware. It can still run on any device that provides VGA or VESA modes.
So, if you want as small of a system as possible using as little power as possible, you're almost certainly better off using X.org built in a minimal fashion or one of the other small X11 servers. However, the size of the screen is irrelevant, as neither X11 nor Wayland cares about policy (how widgets and text and graphics are drawn). The look and feel of the GUI is entirely up to the clients of either X.org or Wayland, which are mostly GNOME ones in the current default Ubuntu desktop, but will be Unity in some later release.
Slashdot Mirror
It's not very interesting to ask whether we should adopt both technologies at the same time, since that's already happening. The transition to IPv6 has been happening for many years, though far too slowly. The transition to DNSSEC just started recently.
The problems are only similar in that the value of adopting either IPv6 or DNSSEC is dependent on the number of other people doing the same. In other words, like most things on the Internet, it's all about network effects. However, the two problems are otherwise orthogonal. DNS (and therefore DNSSEC) is a protocol built on top of IPv4 and/or IPv6. Other than the ability to return either version of IP address, DNS doesn't care which version of IP it's used on.
Fortunately, unlike Lucas, Scott has continued to make a variety of good movies. He hasn't worked on one series his entire career. As long as the writers don't totally suck, these movies will be decent.
Both headlines are incorrect, but the Slashdot one is less so. How often does that happen?
Also, misinformed != stupid. Incredibly, the Slashdot title is more accurate than TFA on that point. I would guess that some misinformed people watch Fox News and some are misinformed as a result of watching it. This produces a feedback loop.
To anyone who believes in a religion, your belief is just as nutty as theirs is to you. You seem to be saying that no one should believe in anything unless they agree with you. Your logic will be consistent as soon as you concede your opinion that all religions are "made up" is just as unfounded as the religions about which you claim this.
Unfortunately, since OpenBSD is one of the projects most fanatical about security audits, it seems unlikely other projects would have caught this.
More importantly, the small amount of CGI in Tron was not intended to look photo-realistic, so it doesn't look dated. Yes, it's very simple by the standard of what can be done today, but the entire look of the world (most of which was not CGI) was intentionally minimalist.
I agree with this completely. I think it's pretty clear that climate change is happening and greenhouse gases released by burning hydrocarbons has a lot to do with it. Though there's plenty of consensus among scientists about that, there is far less about how quickly the climate will change, what the consequences of that will be, and what we should be doing about it.
Icarus Energy!
Not Poseidon Energy?
So, how long will this dream last after the first lawsuit to protect some insect local to the area to be covered by solar panels?
Yes, it's not the USA, but the companies involved in the process will be first world companies, with all the potential for idiotic lawsuits implicit in first world sensibilities....
Japan may be "first world" but, is suing about imagined endangerment of species as common there as in the US? Keep in mind that Japanese people eat a lot of whale, when it's considered taboo almost everywhere else. Also, the Sahara expands constantly as a result of land mismanagement, so I'm sure there's plenty of habitat for both solar cells and insects.
Why DC when AC is better for long distances?
Because AC isn't better for long distances. Perhaps you're confusing alternating current and high voltage.
Now all we have to do is build a massive worldwide network of new transmission lines, stabilize the governments of Africa, and get every country in the world to agree on how the power is to be shared.
Just Northern Africa ;)
Linux Mint will still use GNOME for the forseeable future.
By "still use" do you mean stick with GNOME 2 indefinitely or switch to GNOME 3? I haven't tried either Unity or GNOME Shell yet, but it seems pretty clear that they're both very different from a typical GNOME 2 desktop. I don't think it's fair to characterize Uubntu's switch to Unity as a major change for users in contrast with distributions that switch to GNOME 3.
Lucas didn't direct "Return of the Jedi" either: it was Richard Marquand. According to Lucas, he didn't have time to direct either episode 5 or 6. IMHO, those were the two best because Lucas didn't direct them as well as the fact that Lawrence Kasdan was involved in the writing. What Lucas doesn't explain is why he had time to write and direct the prequels by himself, as they seem to have been much bigger, more complex productions. It seems to me that when he realized his limitations and collaborated with better writers and directors, he obtained the best results, but when he decided he could do it all himself, things went downhill.
Are you implying that Apple owns all iPods, iPhones, and iPads, regardless of how many people think they've purchased them? I suspect that even the most unquestioning Apple fan would balk at the idea that he doesn't own his shiny device.
A very large number of Linux users rely on the proprietary drivers, and the open source drivers will never be as good.
That is a depressing attitude which could become a self-fulfilling prophecy. It's also irrational, as many Linux drivers are superior to their proprietary counterparts. If I believed it, I'd just settle for using OSX (or maybe even Windows) rather than trying to use a Free system. Why would you want to use a system that's always behind?
So, you're really saying that you can avoid a lot of hassle if you just stick to English and ignore all other languages. That has been the attitude of many programmers for decades, but it just isn't good enough any more.
If you were aware of the purpose of Firesheep, you'd know that it is quite effective, since so many large sites don't require the use of HTTPS.
So, what are these crucial features, and which distribution provides them while not running Pulseaudio?
Apple has not gotten it right. I am running several X11 apps on OSX right now and they are second class citizens. Apple has made it very clear that there's only one right way to do things (use their proprietary protocol and libraries) and they don't let you forget it when you run X11 apps. Also, various X11-based desktops have very similar capabilities to Aqua in desktop effects, so dumping X11 is clearly not necessary.
X11 never has and never will depend on TCP/IP. It only depends on some kind of reliable bi-directional byte stream. The common case is a local (Unix domain) socket in the file system, which is very efficient. In that common local case, further optimizations are routinely used via the shared memory X11 extension and graphically intense apps that do things such as play video or display OpenGL graphics usually use direct rendering, which doesn't go through the X11 protocol stream and therefore wouldn't be improved by a switch to Wayland. The proponents of Wayland contend that certain optimizations related to desktop compositing are difficult or impossible when using X11, which seems plausible, but I don't think it's clear that it offers a giant improvement in performance.
Assuming Wayland and the hardware get along, which requires modern Linux interfaces like KMS, and X.org as a Wayland client has full GLX functionality, it should have little effect. That would currently (probably indefinitely) exclude Nvidia proprietary drivers: just one more reason to dump them.
Choice of distribution is one of the great strengths of the GNU/Linux community and I wouldn't recommend Ubuntu for everyone, but it is still entirely possible to turn off Pulseaudio and configure libasound to use hardware devices directly, just as it's possible to use Pulseaudio on Slackware or Gentoo. Also, though Canonical did not transition to Pulseaudio carefully enough, I do think it was a good move overall. Hopefully if they decide to move to using Wayland by default, they will have learned from their mistakes in the Pulseaudio transition.
I also don't think OSX is a good example to follow as I'm using it right now and even on the same machine, X11 clients are second-class citizens. The way to avoid killing remote capability is to leave the X11 client in the widget libraries like Gtk+ and Qt and add the Wayland client, so that apps continue to work with either protocol. As much as Canonical may want it to happen, Gtk+ and Qt (and various other X11 widget libraries) will not suddenly transition to an entirely different protocol.
Apple, starting with the NextStep/OpenStep GUI libraries, had the choice to using an existing windowing system underneath (such as X11) but chose to write a brand new one and only later added X11 as an Aqua client. Canonical has a system based on X11 and wants to transition to a different protocol, but needs to support existing clients, so they shouldn't have an Apple-style attitude that every user and developer is captive to their whims.
I have also played around with Fresco and noticed that while there have been many claims that X11 needs to be replaced and a number of attempts to do so, it has not proven to be necessary and the attempts to replace it have fizzled. I don't know enough about the X11 protocol, the Wayland protocol, or the low level details of managing composition to evaluate how urgently X11 needs to be replaced, but it seems plausible that doing so could allow optimizations that are currently difficult to impossible. Smooth desktop effects on small and/or inexpensive hardware and simultaneous low power usage are great goals, but the need for a change as big as this needs to be well-justified.
In contrast to Fresco, Wayland is nowhere near as ambitious and therefore has a much greater chance of success IMHO. Like X11 and unlike Fresco, it doesn't attempt anything related to GUI policy, but concerns itself only with the low level display manipulation.
I'm sure that to provide adequate backward compatibility, Canonical will need to make sure X.org is available whenever a non-Wayland client needs it and those clients aren't second-class citizens. If they expect all currently used Widget libraries to be adapted to be Wayland clients, that's a huge mistake. It's similar to the transition to using Pulseaudio by default: when libasound clients worked as well as they did talking directly to hardware (which sadly was long after Pulseaudio was run by default), that took care of the majority of transition problems. Hopefully they've learned from their mistakes in that transition and will be more cautious and/or diligent next time.
Also, I'm pretty sure they'll need to allow selection of X.org instead of Wayland to talk directly to hardware on systems that don't have suitable graphics hardware.
X.org was never intended to be a "thin fast X11 replacement", but a fork of XFree which was more modular and easier to add new features to. Both X.org and XFree always have been and always will be X11 servers.
There are several small X11 servers, but Wayland isn't one of them (it is not an X11 server). In contrast with X.org, it actually requires the "super fancy graphics" features, which are present on most new graphics chips, whether on the motherboard or on a big card. X.org never has required anything fancy from the graphics hardware. It can still run on any device that provides VGA or VESA modes.
So, if you want as small of a system as possible using as little power as possible, you're almost certainly better off using X.org built in a minimal fashion or one of the other small X11 servers. However, the size of the screen is irrelevant, as neither X11 nor Wayland cares about policy (how widgets and text and graphics are drawn). The look and feel of the GUI is entirely up to the clients of either X.org or Wayland, which are mostly GNOME ones in the current default Ubuntu desktop, but will be Unity in some later release.