94 karma · joined November 25, 2019
The copyright holders have already gotten paid.
I honestly think the only real solution is re-doing all of it 'from scratch', to make everything (a) stricter and (b) more normal/consistent.
(I think the extant transpilers/preprocessors tend to try to be too 'thin' of a wrapper around CSS/JS: they do give some nice quality of life features but still don't really clean up the mess that is JS and the DOM.)
Wait. VNC is a Windows remote access tool? LOL.
Wait, no, that's America. I was thinking of America.
If so, then a court would have to unseal it.
As an example, in Texas, juvenile records are automatically sealed in most cases, and can basically only be released to the subject of the record, or a prosecutor in a future case.
Sounds like you technically were arrested.
> aren't allowed to use ... sealed court records against you
That's... basically what sealed means.
> California companies aren't allowed to use
Generally the law applies based on the employee's state of residence, not where the company is based.
Anyway... just answer their questions truthfully, but don't disclose anything about sealed records. I highly doubt they'll ask or care about arrests.
"The 379 profitable members of the Fortune 500 paid an effective federal tax rate of 11.3% last year" https://www.axios.com/fortune-500-companies-corporate-income...
Amazon, in particular, made over $10b in 2018, but the US government paid them over $100m.
ETA: And for comparison, I made $36k last year (missed a lot of time for health reasons) with a family of 3 (= negative profit, I'm still in debt from it!), and my tax rate is ~8%.
Instead of having to type <Compose ' o> for a ó, I just type <AltGr+o> (or alternatively, <AltGr+' o>, and similarly <AltGr+` o> for a ò)
Those exist here in the US too. They're just a lot less common. I've had the misfortune of having one, in the past. Needed a new keyboard, went to the store, got the cheapest one, came home to... "what is this layout?!"
When a website uses Markdown for input, it's extremely tough to be sure of how to format certain things, especially when multiple different syntaxes combine. (I'm thinking of things like list+code block; or bold+italics, or list+line break, etc.)
The OP shows errors that are reported to the OS by the drive when it attempts to use the command. Even if it can't pre-determine support for the command, it can fall back upon receiving an error.
This command is not mandated to be supported. Therefore, if an OS assumes it is supported, that's an OS problem, not the drive.
Uhh... well, that math doesn't check out.