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.
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.
Government jobs love them though, Security+ is required for a lot of DoD jobs.