egberts1

3 ms·

1.
by egberts1 7d ago
Then don't worry about it. Your CPU is obviously able to handle your purportedly high-transactional workload ... until it doesn't.
2.
by egberts1 7d ago
Thank you, very much so.
3.
by egberts1 7d ago
Precisely. Fix the browser.
4.
by egberts1 8d ago
Thanks, I needed that!
5.
by egberts1 9d ago
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, ScalableZo
6.
by egberts1 9d ago
Zeow! Citation galore! Gotta RAG them into my LLM! And then THeIR citations too! Thank you very much!
7.
by egberts1 9d ago
Thank you for the insightful aspect. This too should be in the lore of memory allocations as well Will research that, citations and all
8.
by egberts1 9d ago
Lfmalloc? Humalloc? I am intrigued. Is there a source for them?
9.
by egberts1 9d ago
D. S. Hirschberg, A Class of Dynamic Memory Allocation, CACM 16(10) 1973 covered this variants of halving Buddy Allocator.
10.
by egberts1 9d ago
Invariably so but I'm mulling over malloc()s on embedded topic now.
11.
by egberts1 9d ago
It keeps certain web scrapers and inline transparent proxies/IDS/XNS from fetching, 100% Certain browsers will suffer. Meh.
12.
by egberts1 9d ago
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.
13.
by egberts1 9d ago
Thank you for the critique. Compilations are hard to get 100% right.
14.
by egberts1 9d ago
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 B
15.
by egberts1 9d ago
Yes
16.
by egberts1 9d ago
No
17.
Comparison of Malloc() Algorithms(egbert.net)
1 points by egberts1 11d ago|0 comments
18.
Decision Chart of Malloc() Algorithms
1 points by egberts1 11d ago|0 comments
19.
by egberts1 12d ago
Long list of services, 1,200 lawyers https://www.faegredrinker.com/en/services/services
20.
by egberts1 12d ago
One only need to brush up on John Stuart Mill and his "On Liberty (1859). He wrote about individual liberty (before SCOTUS Chief Warren and Brandeis branded the word "privacy" in their 1890 "Rights to Privacy". He s
21.
by egberts1 12d ago
Ditto. Moment we create software liability and enforce them, is that moment AI will ship-up or shape-out )I know it's backward(.
22.
by egberts1 21d ago
Courtesy link for HN readers https://www.rfc-editor.org/info/rfc9539/
23.
by egberts1 25d ago
Once again, private equity ruined another fine company ... with incessant advertisements
24.
by egberts1 25d ago
Electro-mechanical gyroscope
25.
by egberts1 28d ago
Limitation of LLM for and toward reverse engineering; it's the LLM innate error of forgetting states thru agentic recursion by overflow of context or prior premises being optimized away due to not using ternary-state (uninit/writt
26.
by egberts1 1mo ago
LIES! We all know 20% more also means take 20% off gets us the exact same value. NEXT! No? Isn't that the beauty of gullibility?
27.
by egberts1 1mo ago
I think of tokens as fractional digital librarians. None of the analyTical.
28.
by egberts1 1mo ago
At $2,000 (USD), ya think the phone would be gift-wrapped and delivered to you, UNLOCKED?
29.
by egberts1 2mo ago
Or we hope his armpit is infested with fleas from a thousand imaginary camels.
30.
by egberts1 2mo ago
Napkin, someone literally used it at lunch time. Some of us ribbed him: "Destruction of classified material!", "call Security!", "PM's (program manager) behind you". No. Wasnt classified, but company-owned

More ›