I remember this old website that the YouTube team had made which visualised the amount of video time getting uploaded per day on YouTube over the years of its existence, and it was on the order of several years per day or something. Gotta find that site again
Add HMD Nokia to the blocking unlocks completely camp
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
Hyprland, Wayland native Tiling WM
return 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!
'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. <insert description of chatbot>
<insert chat history here>
User: <insert user message here>
Chatbot:
Then it’ll fill in a sentence to best fit that prompt, much like a creative writing exercise
Containers, the concept that Docker implements, lets app developers give a self-contained environment for distribution. For devs that means consistency in deployments across environments, which in turn means sysadmins can deploy each of these apps as fully isolated units.
With that, you get really clean installs/updates/uninstalls, and your deployments get done with a well-defined, declarative definition file which can also handle multi service dependencies (a la Docker Compose/K8s)
That might be more due to them not supporting HDR on Linux yet, but I’ll wait for someone else to confirm that
Ahhh the comment misspelled it, yep that’s the one. Thanks!
I find it funny it didn’t point out Active Directory
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
As an Indian myself this makes me happy :D
From a maintainability standpoint, absolutely. Computers have gotten fast enough to let programmers optimize for developer time instead
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