Skip to content

Commit 1baf3f6

Browse files
committed
doc(readme): Document origin of the project
1 parent 84c2b3b commit 1baf3f6

1 file changed

Lines changed: 14 additions & 0 deletions

File tree

docs/Readme.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,18 @@ Rust's `Vec<T>` types.
77

88
And yeah, project name is subject to change :/.
99

10+
Why? / Origin
11+
-------------
12+
13+
> [![Guess I'm gonna go with C – but damn, there's no std::vector][cppmeme-img]][cppmeme]
14+
>
15+
> --- [programmerhumor.io][cppmeme]
16+
17+
With all seriousness, this literally began as my private library
18+
to deal with the dynamically-sized memory management for data and
19+
data stream buffering in C. It escalated into *my alternative take
20+
on vectors* quickly.
21+
1022
Features
1123
--------
1224

@@ -145,3 +157,5 @@ I might be in need to grant various entities additional priviledges
145157
> feedback).
146158
147159
[CPS]: https://cps-org.github.io
160+
[cppmeme-img]: https://i.programmerhumor.io/2025/11/243e6ff688cb83065c8c4b0965bc97bc4a8066f4deafaf2086a9948245de2ed3.jpeg
161+
[cppmeme]: https://programmerhumor.io/cpp-memes/guess-ill-write-my-own-vector-then-cfec "The eternal struggle of C programmers! You start off all confident like "I'll just write some C code" but then reality hits you with "damn, no std::vector" and suddenly you're implementing your own dynamic array from scratch. It's the classic trade-off: bare-metal performance in exchange for manually managing every byte of memory like some kind of digital janitor. And don't forget the joy of buffer overflows waiting to ambush you like memory landmines! This is why C++ programmers look at pure C coders with equal parts respect and concern for their mental health."

0 commit comments

Comments
 (0)