https://antithesis.com/blog/2026/skiptrees/ #skiplist #datastructure #techhumor #programming #satire #HackerNews #ngated
My memory isn't getting worse, it's just using exponential decay - by Matthew Kim
https://chunkofcoal.com/posts/exponential-decay/
#WebAssembly #WASM #DataStructure #Algorithm #Algorithms #Rust #RustLang
Index, Count, Offset, Size
https://tigerbeetle.com/blog/2026-02-16-index-count-offset-size/
#HackerNews #Index #Count #Offset #Size #DataStructure #Programming
Python Draws Binary Tree Numbers
Hierarchical math creates trees tree structure algorithms create branching patterns that grow like natural trees Tag a Python friend
#python #pythontricks #codingtips #programmingtutorial #binarytree #numbertree #datastructure #pythonart #viralpython #pythonshorts #treepattern
La matematica delle strutture dati racconta una verità semplice: non esiste un modo perfetto per archiviare informazioni.
Ogni sistema è un compromesso tra velocità, memoria e ordine. A volte serve struttura, altre volte un po’ di disordine funziona meglio. Un equilibrio dinamico, in cui l’efficienza nasce proprio dalla varietà delle soluzioni.
https://www.quantamagazine.org/why-theres-no-single-best-way-to-store-information-20260116/
#computerscience #datastructure #data #algorithm #algoritmi #informatica
📜 Discover the Fascinating History of Arrays!
💡 Arrays are everywhere today - from simple algorithms of searching and sorting to technologies like GPUs and AI models.
❓But, one may wonder - what was it like when they were first used?
🔎 Want to know the story behind it?
👉 Check out the article titled: "Story of First Array"
🔗 https://priyabrata-paul-blog.hashnode.dev/story-of-the-first-array
Latest drop from our group 🥳 Paper by Daniel Jünger, Kevin Kristensen, Yunsong Wang, Xiangyao Yu, and Bertil Schmidt
#Bloomfilters are a fundamental #DataStructure for approximate membership queries, with applications ranging from #databases to #genomics.
Bloom filters are a fundamental data structure for approximate membership queries, with applications ranging from data analytics to databases and genomics. Several variants have been proposed to accommodate parallel architectures. GPUs, with massive thread-level parallelism and high-bandwidth memory, are a natural fit for accelerating these Bloom filter variants potentially to billions of operations per second. Although CPU-optimized implementations have been well studied, GPU designs remain underexplored. We close this gap by exploring the design space on GPUs along three dimensions: vectorization, thread cooperation, and compute latency. Our evaluation shows that the combination of these optimization points strongly affects throughput, with the largest gains achieved when the filter fits within the GPU's cache domain. We examine how the hardware responds to different parameter configurations and relate these observations to measured performance trends. Crucially, our optimized design overcomes the conventional trade-off between speed and precision, delivering the throughput typically restricted to high-error variants while maintaining the superior accuracy of high-precision configurations. At iso error rate, the proposed method outperforms the state-of-the-art by $11.35\times$ ($15.4\times$) for bulk filter lookup (construction), respectively, achieving above $92\%$ of the practical speed-of-light across a wide range of configurations on a B200 GPU. We propose a modular CUDA/C++ implementation, which will be openly available soon.
Matching Algorithm with Recursively Implemented StorAge (MARISA) is a space-efficient, fairly fast, and static trie data structure. MARISA serves as a dictionary structure, and by definition, it supports exact match lookup, which is the basic operation of dictionary. In addition, MARISA supports reverse lookup, common prefix search, and predictive search.
Thanks to @terrtia for the discovery.
Grmbl.😩
Implementing an object graph with with loops.
After setup, it needs additional initialization.
The fields getting set will not change again. Ideally would be final (Java, or readonly in TypeScript). And I don't want an "if (bla!=null)" where ever access I them.
In my ideal solution this would be guarded by the type system where the nodes, once initialized, change type. I know roughly how it could be done, but its weird and cumbersome. 😕