If it’s a maximum limit to what’s safe, you can say anything at or below it is safe. They don’t set the maximum at a value that is unsafe for some vehicles.

Government jobs love them though, Security+ is required for a lot of DoD jobs.

The 1m was confiscated because it was ‘illegal income’, not because he used VPN.

Yes, it’s still shitty that using VPN to access GitHub makes his income illegal

using VPN … makes his income illegal

Yes, they fine wasn’t a flat 1m or whatever, but because he earned it while using a VPN on and off(cuz the great firewall periodically blocks github). None of that would of happened if he didn’t use a VPN, so saying that the direct reason he’s in trouble isn’t why he got punished is less honest.

If your complaint is about how the number was determined, perhaps it would be better as “Chinese programmer ordered to pay entire income(1m yuan) for using Virtual Private Network.” Honestly, either headline is fine as long as the details of how that number was chosen is in the article.

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.

They are laying off people not on strike in response to the strike and blaming those on strike for it.

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.

Array.prototype.sort if no callback is passed to it will coerce non-undefined elements to strings when sorting. It does do that.

To sort numbers passing a function like (a, b) => a - b is good enough.