Holy hell
Holy hell
It was initially intended to be a video stream handler, but they had concerns with audio syncing. They figured they might as well also handle audio in one cohesive AV server instead
ret
urn from subroutine, int3 would be something relating to interrupts off the top of my head.
Might want a sled and a ROPe to have a smooth descent
Huh, I was about to correct you on the use of embarrassment in that the intent was to mean a large amount, but it seems a Wiki edit reverted it to your meaning a year ago, thanks for making me check!
I doubt we’ll need a whole different OS for Quantum though. That’s like saying we need a whole separate OS for GPUs. I find it more likely that they’ll be yet another accelerator attached to an orchestrating CPU.
Ahhh the comment misspelled it, yep that’s the one. Thanks!
Ooh can I get an equivalent for zsh? :D
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)
source ~/.bash_history
IIRC, it stands for “If I Remember Correctly”
Bold of you to assume internet access is great everywhere
As an Indian myself this makes me happy :D
Bach Lava Balaklava
Rust has an RFC that wants to consider yeet as a keyword for throwing an exception, I think they’re currently keeping it as a placeholder just in case
Ah I figured I had that one wrong, thanks!
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