egberts1
egberts1 on Hacker News
They shall hereby be termed as "superior digital librarian with a spastic analyst streak"
We're not allowed to talk about it.
There are four lights.
I wonder if the programmer too got brainwashed-failed in ST:NG
Chinese Civil Defense still advocate making inverted A tent in the ground because first 30 minutes count after initial exposure.
Sonarr could have ignored those EXE filetypes, no?
Different Implementation of HTTP requests modules.
That is primarily why websites only TLS-negotiates for server-side-only ChaCha-Poly.
I use RAID1 so that each disk can be pulled and used as standalone.
Different platforms
Tinker, tailor, ...?
CVE bugs should always include the Linux kernel build configuration.
Ya know, such as CONFIG_BLUETOOTH, CONFIG_NAT, as applicable.
Makes decision making so much easier.
UK is doing it wrong.
They would get their best arrest rate with a microphone or printed words.
Camera? We just released a terrorist team spotted by an eyewitness.
/very sarcastcally, sardonically, and facetiously
Should be enough to get a broad socioeconomic category out of that.
Or is public health hiding that too?
Hence my multi-decade long zeal to ban JavaScript ... in web browser.
Then don't worry about it.
Your CPU is obviously able to handle your purportedly high-transactional workload ... until it doesn't.
Precisely.
Fix the browser.
In NextSTEP 3, it was zoned-based allocation.
Rhapsody and early MacOS X, Darwin also used zone-based
Early iPhone also zone-based.
Later MacOS X implemented scalable zone, magazine allocator.
iPhone 12+ then went Nano allocator, ScalableZone + large/VM allocator
Latest iOS/iPadOS use Nano2
Zeow! Citation galore! Gotta RAG them into my LLM!
And then THeIR citations too!
Thank you very much!
Thank you for the insightful aspect. This too should be in the lore of memory allocations as well
Will research that, citations and all
Lfmalloc?
Humalloc?
I am intrigued.
Is there a source for them?
D. S. Hirschberg, A Class of Dynamic Memory Allocation, CACM 16(10) 1973 covered this variants of halving Buddy Allocator.
Invariably so but I'm mulling over malloc()s on embedded topic now.
It keeps certain web scrapers and inline transparent proxies/IDS/XNS from fetching, 100%
Certain browsers will suffer. Meh.
A great idea for another article. A focus, on embedded and malloc()
I do do have a malloc() benchmark but it is in bad shape and directories have not coalesce nicely yet, tor a single run or a menu-driven one.
Thank you for the critique.
Compilations are hard to get 100% right.
Thank you.
I got tired of reading AI prose so I compiled and wrote it from my collections of others' whitepapers.
As a "For Reference Only", at the very least, for me.
As usual, anyone is welcome to improve upon it under CC BY-NC-SA.