A lot of people are in denial that there isn't using some magic efficiency to cloud services that other datacenters don't have. Primary cost savings on cloud VM's is from overprovisioning. The more abstracted away the service is from the hardware, the more they can overprovision without customers noticing.
The 50%+ profit margins have to be coming from somewhere. AWS is not made of magic, it's made from largely the same PC parts you buy on newegg
This is just factually incorrect. AWS hard partitions all instance types, except T2 (which are overcommitted, and clearly advertised as such: "burstable").
So, if you provision an x1.32xlarge with 128 vCPU and 1.92TB of RAM, you get a single, dedicated host with that much CPU and memory. Nobody else gets it - it's dedicated to you 100%.
The profit AWS is making is purely due to datacenter efficiency and being able to automate their operations at scale.
I've been with AWS for about 10 years now on a number of projects. Bandwidth pricing has always been my major gripe. Almost everything else I consider fairly priced for what I get and how hands-off I get to be.
There is nothing stopping Amazon from having a machine that is double that config, and renting you half of it, however.
As soon as 32GB DIMMs drop enough in price, I would expect them to do exactly that. You can configure a Dell R930 with e7 Haswell CPUs online, if you want to double-check it. Not sure if the R930 can go to 8 CPUs (which the e7 Haswells CPUs support).
But as soon as they double the size of the machine there is no reason for them to not have an instance type that is the size of the machine minus the host layer.
well to be honest its because it sounds cool, its in the news, and so how can such proposals be wrong. Seriously the number of times I heard "the cloud" bandied about by people who have continuously failed or were "thwarted" by people who knew better is getting silly. I am sure it happens in other places but too many think it makes them look smart to suggest it.
if anything its a diversion from fixing what is broke or even admitting to it within some organizations
I have a feeling what's happened is that they built something they thought was quantum, but since it's so hard to measure qubits they had to develop a bunch of powerful statistical models to help read the qubits.
These models have gotten so good at reading "correct" results from qubits that they've actually started solving the problems themselves.
So are the qubits actually doing anything now or are the models solving problems from totally random qubit inputs? I think that's a question that even they can't answer
So how long until MS freaks out and starts attacking Linux again? I'm calling GPU DRM modules existing in the next 2 yrs, commonplace in three. Shaders and 3D API inaccessible without the right keys. Only 2D mode and OpenCL without the keys, to "protect" game makers from people running their games on unauthorized platforms. EUFI isn't enough to protect their market share if gaming is threatened, they will extend the lockdown to GPU's as well... for "security"
Linux is still a small share of the Gaming market, I don't think MS feels it is a threat at this stage. As for GPU DRM, is there any indication that manufacturers are moving in that direction ?
I knew what this was going to be before I clicked it...
Old NVIDIA cards flashed to show false specs were showing up in the market, NVIDIA was completely in the right to move towards signed firmware, and while it had an unfortunate effect on an open source effort, it was what had to be done at the time to protect consumers.
instead of messing with JSON and making it less human friendly (arguably the thing that made JSON so popular in the first place), why not just use something designed for efficient machine-to-machine transfer?
Basically making JSON more machine friendly and stricter to parse undermines the original reason to use JSON. If efficiency and absolute correctness are important use something not designed to be forgiving to humans :)
Postel's law: things should parse JSON, but probably only emit SON. That gets you the best of both worlds: you can assume all messages internal to your system are in a canonicalized form (and thus do thing like hashing them with dumb tools), but your system still interoperates with other systems that don't bother to canonicalize, parsing their inputs and sending responses they understand.
You might be interested in JSON5 (http://json5.org/) which goes the opposite direction of Son and makes JSON more human-writeable. It's the best, cleanest "JSON+" I've found so far.
This article has little substance. The arguments don't apply to JWT, it just mentions badly done implementations and an insecure option that obviously nobody would turn on.
What else are we going to use? JWT is basically the simplest token protocol possible that maintains antiforgery properties. It's great that somebody standardized something that most API's were using anyways. If you give anyone that knows crypto the task of making a simple token protocol they will come up with JWT over and over.
Zucks rants about his dream for society scare the hell outta me. It's seriously 1984 type shit... the only way to create "safe" and "friendly" global communities is with bulletproof censorship. Some level of civil disobedience and public disagreement is needed for a properly functioning society. Look up China and "harmonious society" if you don't buy it.
I wish Sergey or Larry from the Goog had such aspirations. At least from what I've read their intentions are pretty benign despite running such a huge monopoly.
A 'counterpoint', such as it is. What makes you think that isn't happening to any 3rd party host you can name? Why single out Cloudflare as adding risk to sites that are hosted on AWS already?
The risk here is real, but it's much more pervasive than one data handler.
You seem to mis-understand how cloudflare works. They allow an insecure host to pose as a secure one and the traffic between cloudflare and the insecure host is not encrypted.
That problem would not exist on 'any 3rd party host'.
CF is the same as any other CDN with TLS termination. Every host that provides a load balancer, or a server, or some other internal network connection like a VPN, can be compromised. Cloudflare is nothing special in this regard.
Having used JS along with somewhere north of 10 other languages over the years... JS is the most painful, even moreso than Perl which was close.
Classes and objects are 100x better than the crap they've come up with to fix JS so far so stop complaining.
Oh no it's not functional???!!! Javascript never was. It was always supposed to be an OO language the implementation is just shit. For the love of God everyone just shut up and let them fix it. Trying to change JS from what it was meant to be into something else entirely is just going to make things even worse
The 50%+ profit margins have to be coming from somewhere. AWS is not made of magic, it's made from largely the same PC parts you buy on newegg