Yes, containers are like jail/chroot. But containers in more recent Linux kernels are now mature enough to almost do all things Solaris Zones does. Like proper security and with use of the http://criu.org/ project, you can also do live-migration in many cases.
The Docker folks actually want to support multiple operating system virtualization technologies.
So Docker doesn't just want to support LXC, if someone wants to write it, they want to support the same on open source Solaris and FreeBSD too for example.
Yes, I think we need some DNSSEC with that too. Not for encryption, but to verify the data (when you route hijack you can easily change some DNS-packets).
The number of attackers that can get attack to the root and tld keys are limited. Yes, it might include NSA and CIA that can get access to the root*, but that probably means it won't be China or Russia.
* Although I don't see a way they can get access to the root signing key and stay undetected, that should deter them. Maybe they can get access to the zone signing keys though, they are valid for a couple of months. As VeriSign and ICANN are both organisations in the US. So they would need get access to those keys at least periodically though.
But the C++ binaries are tied to the processor architecture and don't have a simple delivery process around it. The best they have is: it's pre-installed (like the operating system).
Web technologies do have that, because basically every user-facing device has a browser installed by default.
The operating system on the device people buy already comes with a runtime for running 'web apps', aka browser.
By default you run it in a sandbox and the application running in the sandbox is automatically updated every time you open it. A website is updated on the server, anything that needs downloading again gets downloaded again (even if it's a HTML5 offline 'application').
If the only think you want (which might not apply to you) is other syntax then just transcompile to Javascript. Lots of 'languages' to choose from these days.
Basically low cost, good enough and open platform wins every single time.
Look at the Internet and Linux as just an example.
open platform (which makes for a low barrier to entry): web -> check good enough: web in many, many cases it is -> check low cost: less brain power is needed to create 'web apps' than native apps, so there is a larger base of people you can hire from -> check
But hey, it is the same reason Valve thinks Steam Box can work, because it is an open platform.
Sometimes you want realtime collaboration though, someone to talk to, to show you how to do things, to tell you what you are doing wrong while you are doing it.
Or just straight pair programming.
The web already provides all the pieces: microphone/webcam support, real time communication, just look up webrtc.
Combine that with an online editor like etherpad or more advanced for collaborate online code editor.
Ansible and Salt are very similar. Both are written (mostly) in Python.
What Ansible already had (yaml templates and agent-less/ssh), Salt now also supports (Salt supports multiple templates languages with Yaml as the default I believe).
What Salt has (zmq transport), Ansible now supports (fireball mode).
Yes, containers are like jail/chroot. But containers in more recent Linux kernels are now mature enough to almost do all things Solaris Zones does. Like proper security and with use of the http://criu.org/ project, you can also do live-migration in many cases.
That is exactly the kind of things it is for.
The Docker folks actually want to support multiple operating system virtualization technologies.
So Docker doesn't just want to support LXC, if someone wants to write it, they want to support the same on open source Solaris and FreeBSD too for example.
It is actually used for application containers.
Which means, only the application is started, not a complete userspace.
Making it even more efficient.
While I agree with you.
The real problem is: how do we get all of the public to adopt something like this.
Really, I think it's time for this.
The IETF commited themselves to do so, here are the talks (among the speakers: Bruce Schneier) and discussions:
http://www.youtube.com/watch?v=oV71hhEpQ20#t=23m02s
Here is the voting part:
http://www.youtube.com/watch?v=oV71hhEpQ20#t=2h28m20s
Yes, I think we need some DNSSEC with that too. Not for encryption, but to verify the data (when you route hijack you can easily change some DNS-packets).
The number of attackers that can get attack to the root and tld keys are limited. Yes, it might include NSA and CIA that can get access to the root*, but that probably means it won't be China or Russia.
* Although I don't see a way they can get access to the root signing key and stay undetected, that should deter them. Maybe they can get access to the zone signing keys though, they are valid for a couple of months. As VeriSign and ICANN are both organisations in the US. So they would need get access to those keys at least periodically though.
Ohh, OK, thanks for the information.
It's all about devops these days, right ?
You should be able to get the same environment wherever you are ;-)
Actually, they didn't. They have a way for Visual Studio to control what you do in Azure, as the article says:
"developer services that run on Windows Azure, and extends the capabilities of Visual Studio"
The web technologies are written in C++
But the C++ binaries are tied to the processor architecture and don't have a simple delivery process around it. The best they have is: it's pre-installed (like the operating system).
Web technologies do have that, because basically every user-facing device has a browser installed by default.
Cloud9 IDE is also exists, but a large company pouring money in this space might have an even bigger impact.
At least that is how I see these articles.
Is that runtime pre-installed ? No, it is not, but the browser is. This is an important part of the reason why web technologies are adopted.
Cisco said they would release a free H.264 encoder/decoder:
http://gigaom.com/2013/10/30/mozilla-will-add-h-264-to-firefox-as-cisco-makes-eleventh-hour-push-for-webrtcs-future/
At least free in the sense of: free to download, I don't need to pay MPEG-LA or be worried about their patents.
Cisco is paying for that.
The advantage for the 'web folks' is:
The operating system on the device people buy already comes with a runtime for running 'web apps', aka browser.
By default you run it in a sandbox and the application running in the sandbox is automatically updated every time you open it. A website is updated on the server, anything that needs downloading again gets downloaded again (even if it's a HTML5 offline 'application').
No other runtime has these advantages.
I don't think 'the web people' will need NaCl, they have asm.js.
But the web isn't about the programming languages. It's about the runtime that is already installed everywhere.
If the only think you want (which might not apply to you) is other syntax then just transcompile to Javascript. Lots of 'languages' to choose from these days.
Basically low cost, good enough and open platform wins every single time.
Look at the Internet and Linux as just an example.
open platform (which makes for a low barrier to entry): web -> check
good enough: web in many, many cases it is -> check
low cost: less brain power is needed to create 'web apps' than native apps, so there is a larger base of people you can hire from -> check
But hey, it is the same reason Valve thinks Steam Box can work, because it is an open platform.
Distributed VCS is how collaboration is solved.
Sometimes you want realtime collaboration though, someone to talk to, to show you how to do things, to tell you what you are doing wrong while you are doing it.
Or just straight pair programming.
The web already provides all the pieces: microphone/webcam support, real time communication, just look up webrtc.
Combine that with an online editor like etherpad or more advanced for collaborate online code editor.
But the 'web runtine' (HTML, CSS, JS) is a lot closer than all the other runtimes at being operating system independent.
It usually is just a matter of not using the very latest features. Everything pretty much works.
You are forgetting an other advantage of the web is: there is nothing to install, the runtime is already available.
Buy your own FirefoxOS phone instead of paying your carrier, usually paying for it yourself actually turns out to be cheaper.
At least in Europe SIM-free (unlocked) is a lot cheaper than a subscription with phone.
If you take the difference you pay extra per month, the phone is usually slightly more expensive on contract than off contract.
OK, whatever it is. I just knew I didn't want to look any further ;-)
Well, there is nothing which keeps it directly tied to Ubuntu. But it basically is right now.
Salt and Ansible both support/use Yaml as a template language as a declarative language.
Ansible and Salt are very similar. Both are written (mostly) in Python.
What Ansible already had (yaml templates and agent-less/ssh), Salt now also supports (Salt supports multiple templates languages with Yaml as the default I believe).
What Salt has (zmq transport), Ansible now supports (fireball mode).