AFAIK: Development at AMD funded the dev to make it support AMD GPUs (instead of the then-supported Intel GPUs), Dev keeps a clause saying any and all work will remain open even if contract is cancelled, work is then halted by AMD and dev releases his updates on his repo, Legal then says later that the clause was not legally binding and can't be enforced or such, making dev rollback to earlier Intel version
I coulda swore NASA did account for that and wrote unit conversion subroutines, and that the bug was that a conversion was missed, rather than not knowing the unit mismatch at all
I can't tell if the coaxing thing was an intended pun after the fiber optic thing before it
'tis how LLM chatbots work. LLMs by design are autocomplete on steroids, so they can predict what the next word should be in a sequence. If you give it something like:
Here is a conversation between the user and a chatbot.
User:
Chatbot:
Then it'll fill in a sentence to best fit that prompt, much like a creative writing exercise
Missed opportunity for her to delta outta there instead
- Env vars (maybe)
- Redux
- The dude himself
- Not sure
I'm genuinely having a chuckle at how shocked people are at my submission, made my day xD
To add on to this explanation, you generally use source ~/.bashrc
to reload your shell whenever you want to make changes to your user config. Tab completion weakens the barrier to destruction significantly (esp. in my case)
I feel like that'd defeat the purpose of having redundancy in case the main instance itself goes down 🤔
Android has an Enterprise feature that allows devices to have an isolated "Work" profile from their Personal profile, complete with separate accounts and apps (though your device IDs are still likely shared due to it being the same device)
There's this project called Island that allowed anyone to set it up on their own devices
Trivago? Hotelikely.