'The cloud' does not set up your infrastructure. It does not design or enforce your version control. It does not harden against SQL injection attacks.
Actually there are providers that do, now granted they charge a lot to handle the entire process, but they do exist. A good Platform as a Service (PaaS) provider that handles windows apps (I don't know of any offhand, I'm a Linux/UNIX guy) is what he needs, I'm sure Google can find them.
Other advantages are that the CLI works well over serial lines and SSH, especially low bandwidth and/or high latency connections (you can cut and paste a set of commands and just wait for them to return). Graphic interfaces suck really bad over low bandwidth/high latency (mouse jitter, did I click where I meant to click? did it register the click?). Plus the whole automation bit.
We're better off with DOSbox, emulators tend to last a lot longer than physical hardware. Plus we can just keep layering emulators (DOSBox in Linux in VMware on top of whatever comes next).
What always gets me is this: what if you combine the two? Have a depositor with a pretty fine tolerance (say a 0.1mm nib), and a small CNC unit built into it, say 4 axis. I imagine you could get some pretty insane shapes and really nice tolerances. Especially something that can deposit multiple materials, say wax, plastic, etc. With wax you could then coat it in plaster and sand, melt the object out and voila, you can caste a metal part.
For now, centralizing computing resources in "the cloud" doesn't have the same obvious and conclusive upper hand in the vast majority of common uses that centralized electricity generation does.
It's rapidly happening. You want to do some computing, you can either build a compute farm/etc. (and a server room/building, cooling, electrical, etc, etc.) or just run it on EC2 (which means setting up some non trivial software to handle firing up all the images, monitoring them and their results, setting up storage, etc.), or better yet outsource the whole mess to Cycle Computing (which in turn uses EC2, but handles all the setup/etc. which is non trivial). Compare Cycle Computing at $1,060 an hour (for 10,000 compute cores) and they handle EVERYTHING vs. doing it yourself. http://www.theregister.co.uk/2011/04/06/cycle_computing_hpc_cloud/. Plus you need to remember tax wise operational expenditures are often preferred over capital expenditures, and if your compute farm isn't computing it's a waste of hardware, whereas on EC2 you can provision a ton of systems for the hours or days you need them and then turn them off and stop paying.
When is this "Electrical company" fad going to be over? Trusting someone to run a large scale electrical grid is insane, everyone will keep generating their own electricity! Computing power, storage and bandwidth is becoming a commodity, "cloud" is just a fancy word for infrastructure/commoditization (well and some other issues like elasticity, etc.).
So the oil is not electrically conductive (a good thing right?). What happens when it seeps in between connectors, i.e. into the ram slots or PCIe slots? You start getting really odd random problems, or? How do they address this problem? Also how do you clean the system if you need to service it (i.e. replace bad ram/cards/etc.). If you don't the oils going to get into the slots for memory/cards/etc. when you start swapping components out.
With all the side effects these newer drugs seem to have (rushed warning at the end of the commercials, full page ads with a full page warning on the opposite side) and their cost and dubious effectiveness I really have to wonder how sane people are.
I'm teaching my children that "sharing is caring" and you need to route your Internet traffic through a VPN provider in a country with strong privacy laws.
I'm from Canada using English Firefox/Win7 and I got the url "http://ca.gizmodo.com/#!5787176/this-is-the-moon-and-the-earth-like-you-have-never-seen-them-before" and an article about watches, it wasn't until I scrolled past (counting... 33?) other articles that I got to the one about the space images. This is just fantastically bad.
http://lwn.net/Articles/222773/. Red Hat plays very well with others. Part of the problem is the logistics, with Git and new Kernel development you're looking at literally thousands of source code patches (which would make for a completely unwieldy SPEC file) because Red Hat back ports stuff to keep a stable Kernel in the Enterprise Linux..
http://netalyzr.icsi.berkeley.edu/, requires Java. I personally used this tool to benchmark some consumer router/firewall gear, to find most of it takes 100-300ms to make DNS lookups (which explained why web surfing felt so slow through these things, all the DNS requests were taking about 6x longer than they should).
A lot of what looks like throttling (especially of latency sensitive applications like VOIP) may actually be buffer bloat - http://www.bufferbloat.net/, so while not malicious the end effect is the same (stuff that should work, doesn't).
There's a restaurant local to me - http://www.dadeo.ca/ the best part is "Dadeo Diner & Bar"... "& Bar". No-one under 18 is allowed. So you got great food and no kids. Zero, zilch, nada. The same will hopefully be true for.xxx, imagine an entire set of websites with no kids.....
Since we generally can't just shutdown access to port 80 yet (people would just get errors and confused and angry) there are two methods you can use to transition clients to HTTPS. Use HTTP Strict Transport Security which will address newer clients like Chrome, ideally they access your site securely the first time and you essentially tell them "from now on use HTTPS" for a specific amount of time (the longer the better):
Header set Strict-Transport-Security "max-age=15552000"
Header append Strict-Transport-Security includeSubDomains
The second will address current clients, but will not prevent things like firesheep. However it will hopefully result in people bookmarking your site with HTTPS and so on (take the spaces out between the slashes):
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https: / / %{HTTP_HOST}%{REQUEST_URI} [R=permanent,L]
This should also in theory cause any incoming links from sites that generate them dynamically (e.g. search engines) to take the permanent redirect and update their links (so if someone searches for you and clicks on the link it'll be an HTTPS link)
According to Wikipedia: Employees: 13,500 (2008) (http://en.wikipedia.org/wiki/Kennedy_Space_Center). The national US average of cocaine us is reported as 0.5% or higher (multiple sources but the low end says around 1.5 million users in the US, assuming they are mostly adults that's at least 0.5%, probably more), so statistically speaking that's about 67.5 (assuming one of then only uses one nostril my numbers work =)cocaine users at the Kennedy Space Center.
Opera mini web browser is available for the iPhone and it's a free app. Granted I think it sucks compared to the native Safari, but you do have at least one easy option.
Because they could do it correctly and keep the show moving along nicely, but they choose not to, not really sure why. They do techno babble, might as well make it correct.
Just do a double layer with the joints of the two layers offset, you'd be down to pinpoints of light, which a third layer could solve. Or use tinfoil.
'The cloud' does not set up your infrastructure. It does not design or enforce your version control. It does not harden against SQL injection attacks.
Actually there are providers that do, now granted they charge a lot to handle the entire process, but they do exist. A good Platform as a Service (PaaS) provider that handles windows apps (I don't know of any offhand, I'm a Linux/UNIX guy) is what he needs, I'm sure Google can find them.
Mod parent up
Other advantages are that the CLI works well over serial lines and SSH, especially low bandwidth and/or high latency connections (you can cut and paste a set of commands and just wait for them to return). Graphic interfaces suck really bad over low bandwidth/high latency (mouse jitter, did I click where I meant to click? did it register the click?). Plus the whole automation bit.
We're better off with DOSbox, emulators tend to last a lot longer than physical hardware. Plus we can just keep layering emulators (DOSBox in Linux in VMware on top of whatever comes next).
What always gets me is this: what if you combine the two? Have a depositor with a pretty fine tolerance (say a 0.1mm nib), and a small CNC unit built into it, say 4 axis. I imagine you could get some pretty insane shapes and really nice tolerances. Especially something that can deposit multiple materials, say wax, plastic, etc. With wax you could then coat it in plaster and sand, melt the object out and voila, you can caste a metal part.
I cover how to measure buffer bloat, recreate the problem (trivially easy, in my case a single high speed upload saturates my 3 megabit uplink and ping times go from 50-60ms to 1000+ms. http://www.linux-magazine.com/Issues/2011/127/Security-Lessons-Bufferbloat/%28kategorie%29/0
For now, centralizing computing resources in "the cloud" doesn't have the same obvious and conclusive upper hand in the vast majority of common uses that centralized electricity generation does.
It's rapidly happening. You want to do some computing, you can either build a compute farm/etc. (and a server room/building, cooling, electrical, etc, etc.) or just run it on EC2 (which means setting up some non trivial software to handle firing up all the images, monitoring them and their results, setting up storage, etc.), or better yet outsource the whole mess to Cycle Computing (which in turn uses EC2, but handles all the setup/etc. which is non trivial). Compare Cycle Computing at $1,060 an hour (for 10,000 compute cores) and they handle EVERYTHING vs. doing it yourself. http://www.theregister.co.uk/2011/04/06/cycle_computing_hpc_cloud/. Plus you need to remember tax wise operational expenditures are often preferred over capital expenditures, and if your compute farm isn't computing it's a waste of hardware, whereas on EC2 you can provision a ton of systems for the hours or days you need them and then turn them off and stop paying.
When is this "Electrical company" fad going to be over? Trusting someone to run a large scale electrical grid is insane, everyone will keep generating their own electricity! Computing power, storage and bandwidth is becoming a commodity, "cloud" is just a fancy word for infrastructure/commoditization (well and some other issues like elasticity, etc.).
So the oil is not electrically conductive (a good thing right?). What happens when it seeps in between connectors, i.e. into the ram slots or PCIe slots? You start getting really odd random problems, or? How do they address this problem? Also how do you clean the system if you need to service it (i.e. replace bad ram/cards/etc.). If you don't the oils going to get into the slots for memory/cards/etc. when you start swapping components out.
With all the side effects these newer drugs seem to have (rushed warning at the end of the commercials, full page ads with a full page warning on the opposite side) and their cost and dubious effectiveness I really have to wonder how sane people are.
Will it simulate buffer bloat accurately?
I'm teaching my children that "sharing is caring" and you need to route your Internet traffic through a VPN provider in a country with strong privacy laws.
http://www.wired.com/culture/lifestyle/multimedia/2006/05/fightclub, http://www.msnbc.msn.com/id/13037439/ns/technology_and_science-tech_and_gadgets/, http://www.usatoday.com/tech/news/2006-05-29-fight-club_x.htm.
I'm from Canada using English Firefox/Win7 and I got the url "http://ca.gizmodo.com/#!5787176/this-is-the-moon-and-the-earth-like-you-have-never-seen-them-before" and an article about watches, it wasn't until I scrolled past (counting... 33?) other articles that I got to the one about the space images. This is just fantastically bad.
http://lwn.net/Articles/222773/. Red Hat plays very well with others. Part of the problem is the logistics, with Git and new Kernel development you're looking at literally thousands of source code patches (which would make for a completely unwieldy SPEC file) because Red Hat back ports stuff to keep a stable Kernel in the Enterprise Linux..
Extensive discussion already: http://www.reddit.com/r/programming/comments/g7zlw/google_engineer_releases_open_source_bitcoin/.
http://netalyzr.icsi.berkeley.edu/, requires Java. I personally used this tool to benchmark some consumer router/firewall gear, to find most of it takes 100-300ms to make DNS lookups (which explained why web surfing felt so slow through these things, all the DNS requests were taking about 6x longer than they should).
A lot of what looks like throttling (especially of latency sensitive applications like VOIP) may actually be buffer bloat - http://www.bufferbloat.net/, so while not malicious the end effect is the same (stuff that should work, doesn't).
Granted, but my point was more along the lines that this isn't a small lab with 6 people, it's a town sized institution.
There's a restaurant local to me - http://www.dadeo.ca/ the best part is "Dadeo Diner & Bar" ... "& Bar". No-one under 18 is allowed. So you got great food and no kids. Zero, zilch, nada. The same will hopefully be true for .xxx, imagine an entire set of websites with no kids.....
I think .xxx might work out quite well.
Since we generally can't just shutdown access to port 80 yet (people would just get errors and confused and angry) there are two methods you can use to transition clients to HTTPS. Use HTTP Strict Transport Security which will address newer clients like Chrome, ideally they access your site securely the first time and you essentially tell them "from now on use HTTPS" for a specific amount of time (the longer the better):
Header set Strict-Transport-Security "max-age=15552000"
Header append Strict-Transport-Security includeSubDomains
The second will address current clients, but will not prevent things like firesheep. However it will hopefully result in people bookmarking your site with HTTPS and so on (take the spaces out between the slashes):
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https: / / %{HTTP_HOST}%{REQUEST_URI} [R=permanent,L]
This should also in theory cause any incoming links from sites that generate them dynamically (e.g. search engines) to take the permanent redirect and update their links (so if someone searches for you and clicks on the link it'll be an HTTPS link)
According to Wikipedia: Employees: 13,500 (2008) (http://en.wikipedia.org/wiki/Kennedy_Space_Center). The national US average of cocaine us is reported as 0.5% or higher (multiple sources but the low end says around 1.5 million users in the US, assuming they are mostly adults that's at least 0.5%, probably more), so statistically speaking that's about 67.5 (assuming one of then only uses one nostril my numbers work =)cocaine users at the Kennedy Space Center.
Opera mini web browser is available for the iPhone and it's a free app. Granted I think it sucks compared to the native Safari, but you do have at least one easy option.
Because they could do it correctly and keep the show moving along nicely, but they choose not to, not really sure why. They do techno babble, might as well make it correct.