CheezyWeezle

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

No? It’s literally not a thing on any android. I just pretty extensively looked for any evidence of this online and I can only see people misunderstanding the feature of removing permissions for unused apps. One of the permissions apps are granted is storage, and that permission can get revoked if that feature is turned on. This does not delete stored data (it does not remove data the app has already written) but removes the apps ability to read or write to storage further, and can cause any temporary storage like cache to get erased. This will cause your accounts to get signed out and could potentially lead to data loss, but not because the operating system is actively and purposefully erasing data.

I’m honestly not sure what they are talking about, I’m on Android 14 on my s23 and that isn’t a feature, nor has it ever been on any android phone I’ve ever had or seen. There is an option to remove permissions for apps that have not been used, but not to delete all storage for an app after an amount of time.

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.

They do share a significant commonality, though; they are both interpreted languages, rather than compiled. Sure, you can compile them, but they are meant to be run interpreted so you can quickly and easily tweak and change things and not have to wait for compilation to see the results. In that regard they are very comparable.