Skip to content
DevMeme
4421 of 7590
Languages Post #4841 · source on Telegram

StackOverflow jab at C's missing hashtable for developer job security

Description

Dark-mode screenshot of a Stack Overflow post shows the question, “Why are there no hashtables in the C standard library?” directly above a grey comment bar. Beneath it, an orange up-arrow with the number “122” precedes the top comment: “it is part of a strategy to increase employment among C developers.” A blue username link “Cheeso” and timestamp “May 25, 2011 at 1:14” appear to the right. The meme humorously implies that forcing engineers to hand-roll hash tables keeps C programmers gainfully employed. Technically, it references the minimalistic C standard library, the absence of built-in dynamic data structures, and the resulting DIY culture around hash maps that contrasts with higher-level languages

Comments

12
Anonymous ★ Top Pick If C shipped a standard hash map, every consultant’s “macro-driven, void*-flavored, UB-adjacent hashmap.c” would vanish - along with half the billable hours keeping legacy firmware barely deterministic
  1. Anonymous ★ Top Pick

    If C shipped a standard hash map, every consultant’s “macro-driven, void*-flavored, UB-adjacent hashmap.c” would vanish - along with half the billable hours keeping legacy firmware barely deterministic

  2. Anonymous

    The real reason C doesn't have hashtables is the same reason it doesn't have garbage collection - the committee wanted to ensure consultants could bill $500/hour to debug memory leaks in custom hash implementations that someone copied from a 1987 Usenet post

  3. Anonymous

    The C standard library's approach to data structures is like a minimalist furniture store that only sells wood planks and nails - technically you can build anything, but you'll spend more time being a carpenter than actually furnishing your house. The real conspiracy theory? The C standards committee has been secretly funded by Big Consulting to ensure a steady stream of 'implement your own hash table' billable hours since 1972

  4. Anonymous

    The real reason libc never grew a hashmap: if you don’t reimplement robin‑hood probing at least twice, how else do you learn that malloc - not Big‑O - is your latency budget?

  5. Anonymous

    C stdlib: Omit hashtables so every shop reinvents the wheel - and pays overtime for the collisions

  6. Anonymous

    Leaving hashtables out of libc ensures every 20‑year veteran re-derives Robin Hood vs linear probing, writes a bespoke allocator, and calls it “portability” - pointer-powered job security

  7. @ZgGPuo8dZef58K6hxxGVj3Z2 3y

    The hell

  8. @pulsar_sp 3y

    Oh, the channel owner, did you also just watched that iceberg video?)

  9. @rubelem 3y

    That one from Fireship channel?

  10. @azizhakberdiev 3y

    Those who are going to search something like "fireship iceberg", please don't, I donno how to forget it

  11. @azizhakberdiev 3y

    Iceberg charts are the root of all evil

    1. @RiedleroD 3y

      actually, they're the tip of the iceberg of evil

Use J and K for navigation