I didn’t see the replies to me, but the person i responded to posted the raw uncensored output of a traceroute from their computer to twitter, and I heavily suggested that they should not do that and should remove or edit their comment.
Removed by mod
Kind of. With hoisting, the compiler/interpreter will find variable declarations and execute them before executing the rest of the code. Hoisting leaves the variables as undefined until the code assigning the value to the variable is executed. Hoisting does not initialize the variables.
For example:
console.log(foo);
var foo;
//Expected output: console logs ‘null’
foo = ‘bar’;
console.log(foo);
var foo;
//Expected output: console logs ‘bar’
console.log(foo === undefined);
var foo;
//Expected output: console logs ‘true’
This means you can essentially write your code with variable declarations at the end, but it will still be executed as though the declarations were at the beginning. Your initializations and value assignments will still be executed as normal.
This is a feature that you should probably avoid because I honestly cannot think of any good use case for it that won’t end up causing confusion, but it is important to understand that every variable within your scope will be declared at the beginning of execution regardless of where it is written within your code.
Eh, this particular screen is kind if misleading. You say you dont see a “skip” or “do not remind again” button, well that’s because those buttons are on the next screen(s) for each individual feature. I’ve gotten this screen a couple times, just click through and you can skip/opt out of all the features. It’s kind of silly, but I think the point is that they want you to look at each new feature individually.
SLA contracts can have a plethora of stipulations, including fines and damages for missing SLO. It really depends on how big and important the customer is. For example, you can imagine government contracts probably include hefty fines for causing downtime or data loss, although I am not involved with or familiar with public sector/ government contracts or their terms.
You can imagine that a customer that is big enough to contract a cloud provider to build new locations and install a bunch of new hardware just for them, would also be big enough to leverage contract terms that include fines and compensation for extended downtime or missing SLO.
I work at a data center for a major cloud provider, also not AWS