Lmao you are actually incapable of good faith, probably because of how obviously angry you are hahaha
You are still trying to argue that your idealized theoretical version of communism is what needs to be accepted, but that a corrupted and condemned version of capitalism is what capitalism is inherently at its core. By your own standard, communism is equally abhorrent because of how it has been actually implemented in the past.
A company getting bailed out is not capitalism. It is socialism. A capitalist society implementing corporate socialism is a corruption of the core ideology of capitalism. I will agree that it is the end goal of corporatism, but corporatism is a corruption of capitalism.
And wow you really still don’t get the “no true scotsman” thing… I mean you probably do but once again, you are only putting bad faith forward. Since you clearly need it spelled out in detail, let me just copy this excerpt from the Wikipedia article on “No true Scotsman”:
The “no true Scotsman” fallacy is committed when the arguer satisfies the following conditions:[7][3][4]
not publicly retreating from the initial, falsified assertion
offering a modified assertion that definitionally excludes a targeted unwanted counterexample
using rhetoric to hide the modification
Oops, you accidentally did all those things. You never retracted your assertion, you modified the assertion with further qualifiers, and tried to downplay that further qualification. You actually pulled a “no true scotsman” on a statement about someone being a scotsman. It’s so on the nose that you MUST be a troll lmao
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.