I'm pretty sure what's being alleged is that there is real data exfiltrated from his devices on the laptop, but the laptop itself wasn't his. As in he was hacked, someone created the laptop with that data and added manipulations to it, then coincidently dropped it off to be "found".
Given the lack of proper chain of custody, it's probably likely.
I think he means that a 90% drop would be 90 Mbps. This is more like a 7% drop.
It's a contract thing called detrimental reliance. As I understand it, basically you relied on a promise to do something only in the event the promise was upheld then it wasn't. It wouldn't hurt to speak to a lawyer for a consultation. I doubt you'd get the job back, but they could be liable for the damages caused by moving.
Hey, I love that they added the effect of his clothes dropping off him the first time he shape-shifts after regaining his shape-shifting abilities.
While the concept as capitalism didn't exist, there are certainly many facets of the ancient economy that are facets of capitalism.
Most of the economy was privately held, just certain facets of modern capitalism like corporations didn't exist.
So, while you are technically true, you know exactly what they are talking about. We can't 100% relate, but issues like laborers getting a fair wage and the rich exploiting the poor were just as relevant then as now.
They are laying off people not on strike in response to the strike and blaming those on strike for it.
Why not do both?
You are probably correct. I don't know if it's true, it's probably more likely it was a way for it not to fail.
I said HTTP mainly because HTML is plaintext because of it. 1.0s main purpose was to manipulate the page. Of course Array objects weren't added til 1.1, when netscape navigator 3.0 released, but it was still mostly 1.0 code. I felt like having everything be coercable to string made it easy for you to just assign it to the document. If you assigned the wrong thing it wouldn't crash.
I originally thought there was a precursor to microsofts XMLHTTP in an earlier version due to the 1997 ECMAScript documentation specifically talking about using it both client and serverside to distribute computations, but it was far more static. So, I'm probably just wrong.
Mainly because JavaScript was designed to work along side HTTP in a browser. Most of its input will be text, so defaulting common behavior to strings makes some sense.
functools.cache
That's pretty cool. I haven't dived too deep into python, so I should of looked up the library when you attached the @cache decorator. I learned something.
Lol at mobile autocorrect, I wanted to say exfiltrated.