CheezyWeezle

I mean that would hardly hold up to a challenge fir inadequate consideration. The value of all intellectual property in perpetuity is easily worth far more than access to the reddit website.

I got something stupid like a 96 on the ASVAB and I just told the first air force guy I smoked a lot of weed and I never heard from any military again lmao

It was tempting when they offered me to go right into a program to become a satellite operator starting off making $125k/year immediately after boot camp… but I don’t regret not taking that offer. Who knows what would have actually materialized, anyways. Probably would have been 6 years deep dreaming of hopefully seeing 6 figures one day while I end up managing logistics or something.

I never said this was a bad value, but I think we all know that these prices will not remain. They will increase because people will pay it once they are locked in. And if someone buys a used car, they have to pay that subscription to get these features, ensuring the manufacturer gets a slice from used sales. I can understand the cost, but it sets a dangerous precedent. It should be one time fee that grants the VIN access to the severs permanently. What would be really nice is if we had legislation that requires companies with a certain amount of revenue to maintain services for older products so they can’t just pull the plug later anyways.

I can understand some of these features requiring a $5/month subscription. Anything more than that is absolutely insane. With roadside assistance (depending on what that actually entails) I could see that sevice being bumped to $15-$20 a month,

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.