From single photons, to complete atoms, to complete molecules, to a proof of concept on something that could be called alive (or at least working enough to be able to reproduce in the right environment). Each one of those steps are pretty big jumps in complexity, that may bring their own showstoppers to the party. But probably will give hard numbers to the real impossibility of teleporting humans.
If well this is a particulary human harming virus, and in concentrated dosis, let not forget that each drop of sea water have 10 millon virus and 1 millon bacterias (and, hopely, most won't be harmful for humans). We live in a world with them.
Anyway, what would be the difference between a big corporation doing that by mistake or not, or terrorists announcing that they did exactly the same? Effective or not, that should had been ranked as a biological weapon attack.
1 millon is a very big number. Mankind odds for the future could be vastly improved if we send maybe 1000 (specific) people to Mars. Or to the bottom of the sea, or maybe just sacrifice them in a volcano.
Seriously, for sending big amounts of people and materials elsewhere you need more than rockets, maybe an space elevator, or a cheaper/more efficient way to send big loads to space (there are several alternatives for non-rocket spacelaunch)
The vulnerability is in the language parser, not the language design by itself. Imagine that in java (or whatever is a "proper" designed language for you, just that don't be PHP) you put some weird syntax that makes the compiler to execute injected code.
And with linux, as long as you install from your distribution (that already have most if not all that you will ever need to install), you have security fixes for all of what you have installed, not just the kernel or a minimal core of apps.
Firefox OS It is already on market, and is probably very used on markets like India and South America
And to understand why it matters you must understand the players. The manufacturers are providing cheap phones where they can run without the restrictions/conditions of WP/Android, same goes for carriers (that are actively pushing Firefox OS phones in emergent markets), and developing apps considering that is Firefox OS around means doing open, multiplatform web apps, not just for one OS/device, that is in the end Mozilla's goal, if Ubuntu touch means more html apps, then it will be something possitive for Mozilla.
You can access and install apps from the Firefox Marketplace on Android, it turned Firefox OS irrelevant, or made it more relevant than before?
It runs in different fronts. With WP8 is battling against an unified desktop/mobile OS (something that iOS and Android aren't doing). With Sailfish/Tizen is battling for developers of QT/linux environments (and getting enough developers will be good for all 3 platforms),
And as any race, your immediate objective is to catch the ones that are right infront of you, not the ones that are on top, To be the 3rd mobile platform is a good near term objective.
The fact is that the planet is trapping more heat due to more greenhouse gases. The actual manifestations of it may vary with time. But eventually all heat sinks will saturate. And that wont be nice.
Not just thin. The time has come for cluster-targetted distributions. Openstack, CoreOS and others are minimal linux meant to do mostly a supporting work for loading over them as VMs or container clouds the more bulky application linux servers/images/containers. All is about having a bunch of servers (real or virtual), installing something minimal that builds a cloud on them. It's linux all way down.
You already have a privacy vanishing cellphone connected with privacy destroyer social networks. But cars are destructive in the real world. Can be used to kill you or others blaming you, or just put you in jail.
This kind of people have government-approved full access to the (potentially naked) selfies of all underage girls of the entire world, celebrity or not, and they surely abuse of it. And are supported for doing that.
Was my biggest concern. Shortly after it got discovered was concluded that won't hit us. But we got a short time notice, in the case that it would be precisely calculated where it would land, and that be over/near a big city (even with the low odds of it), would be no way to stop it, and for some scale of cities 1 week of advice won't be enough (or will do by itself enough damage).
We should hope that bigger/more damaging rocks should be more visible and that we get aware of them with more anticipation, but in the other hand, we are using now the money that we could invest in detect or even avoid that kind of end of the world scenarios on saving banks of their own risk taking or creating new wars.
LXC existed for some years so far, and the same for containers and similar technologies in other platforms. What Docker added over lxc is adding the use of an unionfs for reusing/improving containers, a simple way to share them, and a simple but powerful command line utility and api to manage them.
There is nothing so special in sulphur, charcoal and salt peter, but do the right mix with them and you get something explosive (and used in revolutions, too)
Considering the average adult that went through the Ice Bucket Challenge, it would be a great advice for them too. I won't be surprised at all if it ends killing more people than ALS.
You forgot to name OpenVZ too, that is older than Solaris Zones. And Docker is originally based on LXC, that have several years. But is more than just containers, the layered copy-on-write union filesystem have a lot of practical advantages, the git-like repository for images redefines app packaging and the simple api is flexible enough to spawn a lot of projects that improved the ecosystem a lot in the last year.
The idea of containers is that full virtualization requires too much resources. Put your apps in its own filesystem/network/users/processes/memory/etc in an efficient way (adding cow/union fs to the mix is one of the big advantages of docker) and you are running at basically native speed, using very little extra disk (i.e. 2 vms running ubuntu have the full copy of ubuntu each, even deduplication don't match the saving you do with different containers sharing the same base), and memory (just one kernel loaded, the memory you use is just the app one). You just can do far more density of "virtualized" applications in real or virtualized hardware than using VMs.
But as they run under the same kernel, you can run only linux apps with it (with vms you can run windows or *BSD), and have a bigger exposure area in the kernel than VMs. Adding this new security features should lower the risk of exploiting containers to get access to the main machine. The other alternative is to run multiple containers in VMs to lower exposure while maximizing application density, a bit of what Google does. And the fact that you can run containers in VMs mean that you can run them on AWS, google app engine and other cloud services that give you essentially VMs instead of bare metal.
Another option is to move VMs to the container advantages zone, like creating microVMs to run single applications (like in OpenMirage)
You can download Docker source code, compile it yourself, have your own image repository, and even copy just the dockerfiles to put big/complex installations under your supervision/control rebuiding/tuning them yourself
What docker does is provide a "walled garden" for applications from other people/companies running in your own servers/desktops, limiting what they can do with your system and data, like a lightweight VM. The focus of this article is how to impove the security of that "walled garden" even more.
Complex ones are still relevant, like language, religion and moral, even if the internet ones are more documented and have a more delimited life cycle. And they are risk to get their funds cut when they find the truth behind the ice bucket challenge,
The point of Docker and containers in general is that they are running at basically native performance. There is no vm, no virtualized OS, you run under the main OS kernel, but it don't let you see the main OS filesystem, network, processes and so on, and don't let you do operations risky for the stability of the main system. There is some overhead in the filesystem access (in the case of docker, you may be running on AUFS, device mapper, or others that will have different kind of impact in several operations), but still is a far cry from VMs using a filesystem on a file of the main system with its own filesystem driver.
Add to that how police cover up miscarriages and that you can'tfilm the police, is not just who watches the watchers, but who watches the watchers that have military-grade weapons in the streets and are abusing of them.
Slashdot Mirror
Anyone that complain about government, denounce abuses, disagree with GHCQ surveillance and so on will be considered trolls.
The NSA did it before, and keep doing it.
From single photons, to complete atoms, to complete molecules, to a proof of concept on something that could be called alive (or at least working enough to be able to reproduce in the right environment). Each one of those steps are pretty big jumps in complexity, that may bring their own showstoppers to the party. But probably will give hard numbers to the real impossibility of teleporting humans.
If well this is a particulary human harming virus, and in concentrated dosis, let not forget that each drop of sea water have 10 millon virus and 1 millon bacterias (and, hopely, most won't be harmful for humans). We live in a world with them.
Anyway, what would be the difference between a big corporation doing that by mistake or not, or terrorists announcing that they did exactly the same? Effective or not, that should had been ranked as a biological weapon attack.
1 millon is a very big number. Mankind odds for the future could be vastly improved if we send maybe 1000 (specific) people to Mars. Or to the bottom of the sea, or maybe just sacrifice them in a volcano.
Seriously, for sending big amounts of people and materials elsewhere you need more than rockets, maybe an space elevator, or a cheaper/more efficient way to send big loads to space (there are several alternatives for non-rocket spacelaunch)
The vulnerability is in the language parser, not the language design by itself. Imagine that in java (or whatever is a "proper" designed language for you, just that don't be PHP) you put some weird syntax that makes the compiler to execute injected code.
The Microsoft that delays releasing patches for zero-day vulnerabilities so the NSA can exploit them first? The one that took 7 years to fix a known vulnerability? The one that took 7 months to fix a remote IE exploit after it was reported, just because it wasn't public enough?
And with linux, as long as you install from your distribution (that already have most if not all that you will ever need to install), you have security fixes for all of what you have installed, not just the kernel or a minimal core of apps.
Firefox OS It is already on market, and is probably very used on markets like India and South America
And to understand why it matters you must understand the players. The manufacturers are providing cheap phones where they can run without the restrictions/conditions of WP/Android, same goes for carriers (that are actively pushing Firefox OS phones in emergent markets), and developing apps considering that is Firefox OS around means doing open, multiplatform web apps, not just for one OS/device, that is in the end Mozilla's goal, if Ubuntu touch means more html apps, then it will be something possitive for Mozilla.
You can access and install apps from the Firefox Marketplace on Android, it turned Firefox OS irrelevant, or made it more relevant than before?
Considering that you can install ubuntu touch in several of the existing android phones, it is already battling with Android on the installed base.
It runs in different fronts. With WP8 is battling against an unified desktop/mobile OS (something that iOS and Android aren't doing). With Sailfish/Tizen is battling for developers of QT/linux environments (and getting enough developers will be good for all 3 platforms),
And as any race, your immediate objective is to catch the ones that are right infront of you, not the ones that are on top, To be the 3rd mobile platform is a good near term objective.
The fact is that the planet is trapping more heat due to more greenhouse gases. The actual manifestations of it may vary with time. But eventually all heat sinks will saturate. And that wont be nice.
Not just thin. The time has come for cluster-targetted distributions. Openstack, CoreOS and others are minimal linux meant to do mostly a supporting work for loading over them as VMs or container clouds the more bulky application linux servers/images/containers. All is about having a bunch of servers (real or virtual), installing something minimal that builds a cloud on them. It's linux all way down.
You already have a privacy vanishing cellphone connected with privacy destroyer social networks. But cars are destructive in the real world. Can be used to kill you or others blaming you, or just put you in jail.
I suppose that it explain all the buzz around dark energy.
This kind of people have government-approved full access to the (potentially naked) selfies of all underage girls of the entire world, celebrity or not, and they surely abuse of it. And are supported for doing that.
Was my biggest concern. Shortly after it got discovered was concluded that won't hit us. But we got a short time notice, in the case that it would be precisely calculated where it would land, and that be over/near a big city (even with the low odds of it), would be no way to stop it, and for some scale of cities 1 week of advice won't be enough (or will do by itself enough damage).
We should hope that bigger/more damaging rocks should be more visible and that we get aware of them with more anticipation, but in the other hand, we are using now the money that we could invest in detect or even avoid that kind of end of the world scenarios on saving banks of their own risk taking or creating new wars.
LXC existed for some years so far, and the same for containers and similar technologies in other platforms. What Docker added over lxc is adding the use of an unionfs for reusing/improving containers, a simple way to share them, and a simple but powerful command line utility and api to manage them.
There is nothing so special in sulphur, charcoal and salt peter, but do the right mix with them and you get something explosive (and used in revolutions, too)
Considering the average adult that went through the Ice Bucket Challenge, it would be a great advice for them too. I won't be surprised at all if it ends killing more people than ALS.
1 cubic light year of water should weight thousands of times more than it, at least if there is enough oxigen in the universe to make that cube.
You forgot to name OpenVZ too, that is older than Solaris Zones. And Docker is originally based on LXC, that have several years. But is more than just containers, the layered copy-on-write union filesystem have a lot of practical advantages, the git-like repository for images redefines app packaging and the simple api is flexible enough to spawn a lot of projects that improved the ecosystem a lot in the last year.
The idea of containers is that full virtualization requires too much resources. Put your apps in its own filesystem/network/users/processes/memory/etc in an efficient way (adding cow/union fs to the mix is one of the big advantages of docker) and you are running at basically native speed, using very little extra disk (i.e. 2 vms running ubuntu have the full copy of ubuntu each, even deduplication don't match the saving you do with different containers sharing the same base), and memory (just one kernel loaded, the memory you use is just the app one). You just can do far more density of "virtualized" applications in real or virtualized hardware than using VMs.
But as they run under the same kernel, you can run only linux apps with it (with vms you can run windows or *BSD), and have a bigger exposure area in the kernel than VMs. Adding this new security features should lower the risk of exploiting containers to get access to the main machine. The other alternative is to run multiple containers in VMs to lower exposure while maximizing application density, a bit of what Google does. And the fact that you can run containers in VMs mean that you can run them on AWS, google app engine and other cloud services that give you essentially VMs instead of bare metal.
Another option is to move VMs to the container advantages zone, like creating microVMs to run single applications (like in OpenMirage)
You can download Docker source code, compile it yourself, have your own image repository, and even copy just the dockerfiles to put big/complex installations under your supervision/control rebuiding/tuning them yourself
What docker does is provide a "walled garden" for applications from other people/companies running in your own servers/desktops, limiting what they can do with your system and data, like a lightweight VM. The focus of this article is how to impove the security of that "walled garden" even more.
What If, not exactly the classic xkcd comics, but worthy a book even if he don't expand even more the articles over what was posted in that site.
Complex ones are still relevant, like language, religion and moral, even if the internet ones are more documented and have a more delimited life cycle. And they are risk to get their funds cut when they find the truth behind the ice bucket challenge,
The point of Docker and containers in general is that they are running at basically native performance. There is no vm, no virtualized OS, you run under the main OS kernel, but it don't let you see the main OS filesystem, network, processes and so on, and don't let you do operations risky for the stability of the main system. There is some overhead in the filesystem access (in the case of docker, you may be running on AUFS, device mapper, or others that will have different kind of impact in several operations), but still is a far cry from VMs using a filesystem on a file of the main system with its own filesystem driver.
When the only tool you have is a hammer, everything looks like a nail. Now police's only tool are military-grade weapons, intended to kill.
And sometimes the situation changes how people is, like in this Standford prison experiment
Add to that how police cover up miscarriages and that you can't film the police, is not just who watches the watchers, but who watches the watchers that have military-grade weapons in the streets and are abusing of them.