this post was submitted on 28 Dec 2025
398 points (95.6% liked)

Programmer Humor

28114 readers
1342 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 

Post:

If you’re still shipping load‑bearing code in C, C++, Python, or vanilla JavaScript in 2025, you’re gambling with house money and calling it “experience.”

As systems scale, untyped or foot‑gun‑heavy languages don’t just get harder to work with—they hit a complexity cliff. Every new feature is another chance for a runtime type error or a memory bug to land in prod. Now layer LLM‑generated glue code on top of that. More code, more surface area, less anyone truly understands. In that world, “we’ll catch it in tests” is wishful thinking, not a strategy.

We don’t live in 1998 anymore. We have languages that:

  • Make whole classes of bugs unrepresentable (Rust, TypeScript)
  • Give you memory safety and concurrency sanity by default (Rust, Go)
  • Provide static structure that both humans and LLMs can lean on as guardrails, not red tape

At this point, choosing C/C++ for safety‑critical paths, or dynamic languages for the core of a large system, isn’t just “old school.” It’s negligence with better marketing.

Use Rust, Go, or TypeScript for anything that actually matters. Use Python/JS at the edges, for scripts and prototypes.

For production, load‑bearing paths in 2025 and beyond, anything else is you saying, out loud:

“I’m okay with avoidable runtime failures and undefined behavior in my critical systems.”

Are you?

Comment:

Nonsense. If your code has reached the point of unmaintainable complexity, then blame the author, not the language.

top 50 comments
sorted by: hot top controversial new old
[–] echodot@feddit.uk 18 points 1 day ago (1 children)

So there is apparently a problem with languages such as JavaScript and the solution is to use languages such as TypeScript.

Wut?

[–] keegomatic@lemmy.world 12 points 1 day ago* (last edited 1 day ago) (1 children)

Well, yes. TypeScript mitigates one big problem with JavaScript (type safety). That’s why it exists. It’s a dumb idea to choose vanilla JS over TS if you’re starting a new project today, IMO.

Whether or not you should use TS as your core language is debatable and situational, but in terms of using TS instead of JS, yeah, that’s a no brainer.

[–] pelya@lemmy.world 35 points 2 days ago (2 children)

TypeScript and safety-critical paths should not be in one sentence.

load more comments (2 replies)
[–] ExLisper@lemmy.curiana.net 62 points 2 days ago (4 children)

Just don't do bugs. How hard is that?

[–] douglasg14b@lemmy.world 11 points 1 day ago

According to all teams I've worked on.

Pretty fucking hard.

I know this is satire, But really though better languages that make various classes of defects unrepresentable reduce defects. It's wild that such a statement needs to be made, but our industry is filled with folks who don't critically think about decisions like these.

[–] Phunter@lemmy.zip 3 points 1 day ago (1 children)

If I don't have documentation or defined features, then I can't do bugs!

[–] Tlaloc_Temporal@lemmy.ca 2 points 1 day ago

The evolution strategy: if you don't know what you're doing, every function is a feature!

[–] MIDItheKID@lemmy.world 11 points 2 days ago

Like the age old advice for getting better at Smash Brothers - Don't get hit.

load more comments (1 replies)
[–] Scrath@lemmy.dbzer0.com 65 points 2 days ago (13 children)

As an embedded dev, good luck not using C

load more comments (13 replies)
[–] sheepishly@fedia.io 21 points 2 days ago (2 children)

don't just m-dash

chat gippity

[–] chatokun@lemmy.dbzer0.com 17 points 2 days ago (1 children)

Maybe, but always remember LLMs are trained on real people. Some people naturally use similar styles to some LLM tica as it was stolen from them in the first place.

[–] Bazoogle@lemmy.world 1 points 1 day ago (1 children)

If you see more than 3 EM dashes in a body of text, it's 100% AI. I have found random online articles where there is at least two em dashes every paragraph. No human wrote that shit. A human is lucky to get away with one em dash (and it's been that way before AI).

[–] andioop@programming.dev 7 points 1 day ago

one heartbroken anti-AI human who loves em dashes replying ☹️ we're split into two classes: the type who abandons our typing habits to avoid being told our human efforts are definitely AI, and the type who stubbornly carries on using em dashes

[–] Ashelyn@lemmy.blahaj.zone 9 points 2 days ago

Don't just state—regurgitate!

[–] jonathan7luke@lemmy.zip 119 points 2 days ago (1 children)

I'm not even going to bother commenting on that train wreck of a post, but I just wanted to mention that I hate the writing style of programming-related LinkedIn posts. They're just chock-full of sweeping generalizations presented as absolute truth in an extremely patronizing tone.

Why can't people just say, "In my opinion, X technology is a better fit for Y situation for Z reason," instead of "Every time you encounter X, you must do Y, otherwise you're dead wrong."

It's just simultaneously so arrogant and also aggressively ignorant. If someone spoke to me like that in real life, I would never want to speak with them again. And these people are broadcasting this shit to their entire professional network.

[–] Ephera@lemmy.ml 29 points 2 days ago

Yeah, particularly the broadcasting really irks me.
That is an opinion you can hold for yourself and then make compromises as you encounter reality. I do expect programmers to hold strong opinions.

But when you broadcast it, you strip yourself of the option to make compromises. You're just saying something which is going to be wrong in one way or another in most situations. I do expect programmers to be smarter than that.

[–] Shirasho@lemmings.world 105 points 2 days ago* (last edited 2 days ago) (5 children)

"Blame the author, not the language"

Says the person who screams they have never worked professionally with a team before.

There is no excuse to not use statically typed, safe languages nowadays. There are languages that let you build faster like Python and Typescript, but faster does not mean safer. Even if your code is flawless it still isn't safe because all it takes is a single flawed line of code. The more bug vectors you remove the better the language is.

[–] Arkouda@lemmy.ca 70 points 2 days ago (2 children)

Even if your code is flawless it still isn’t safe because all it takes is a single flawed line of code.

If there is a single flawed line of code, the code isn't flawless.

load more comments (2 replies)
[–] rtxn@lemmy.world 37 points 2 days ago (3 children)

let you build faster like Python

I have to write so much boilerplate code to make sure my objects are of the correct type and have the required attributes! Every time I write an extension for Blender that uses context access, I have to make sure that the context is correct, that the context has the proper accessor attributes (which may not be present in some contexts), that the active datablock is not None, that the active datablock's data type (with respect to Blender, not Python) is correct, that the active datablock's data is not None... either all that or let the exception fall through the stack and catch it at the last moment with a bare except and a generic error message.

I used to think that static typing was an obstacle. Now I'm burning in the isinstance/hasattr/getattr/setattr hell.

load more comments (3 replies)
[–] BassTurd@lemmy.world 37 points 2 days ago (18 children)

There are definitely use cases where something like C is still the best option because it's faster. For the most part consumer software it's unnecessary, but it's not obsolete for all applications.

load more comments (18 replies)
load more comments (2 replies)
[–] grue@lemmy.world 75 points 2 days ago (11 children)

Python isn't "untyped;" it is, in fact, strongly-typed. (And is markedly different than and superior to JavaScript on that point.)

This rant feels like it was written by an OO programmer who was never able to wrap his head around functional programming.

[–] Badabinski@kbin.earth 37 points 2 days ago (3 children)

Yeah, plus it has type hints and tooling to make said type hints mandatory.

Also, like, fuck golang, it's such a shit language and the compiler does very little to protect you. I'd say that mypy does a better job of giving you AOT protection.

load more comments (3 replies)
load more comments (10 replies)
[–] Atlas_@lemmy.world 21 points 2 days ago (1 children)

Go and Python and Typescript all have their own footguns.

I assume Rust is the same, but haven't used it personally to see

[–] danhab99@programming.dev 17 points 2 days ago (1 children)

Rust is the foot gun, it's so perfect that you genuinely cannot just sit down and type out what you need.

[–] fnrir@lemmy.blahaj.zone 2 points 1 day ago* (last edited 1 day ago) (1 children)

Skill issue

- sincerely, someone making a DST crate

EDIT: To clarify...

There are some things that are only doable on nightly Rust (like specialization, const fn in traits, etc.) and the reason for that is to avoid future issues. In that regard, Rust will not be as good as C++... at least until those get stabilized.

Some of the nightly functionality (like ptr_metadata) can be achieved with unsafe code and it's fine to do that, as long as it's only done when necessary and it's properly documented.

It's okay to want to use C++, but that language has it's own issues and footguns (virtual destructors, "move semantics", C-style casts, header files and more) that Rust wants to avoid.

EDIT 2: Specialization is also kinda doable with deref coercion, but that's another can of worms I don't wanna open here.

EDIT 3: And if I had to mention some of Rust's footguns:

  • unwrap panics, which isn't bad in and of itself, but it's short so you'll probably want to use it instead of other error handling methods (see recent Cloudflare outages)
  • unsafe functions implicitly allows using unsafe operations (fixable by adding #! [deny(unsafe_op_in_unsafe_fn)])
[–] darvit@lemmy.darvit.nl 1 points 17 hours ago

For my own Rust project I require myself to have a comment for every unwrap call that explains why that unwrap will never panic. For everything else I let the function return an error, with help of the anyhow crate and error contexts.

[–] Zos_Kia@lemmynsfw.com 42 points 2 days ago (3 children)

it's just negligence with better marketing

Good damn I hate that tone it reeks of LinkedIn llm-powered personal branding. Weak ideas with writing that tries to sound strong is the worst.

load more comments (3 replies)
[–] for_some_delta@beehaw.org 21 points 2 days ago (3 children)

I don't get it.

Maybe the joke is nothing complex is written in fad languages?

Maybe the joke is the discounting of peer review and testing?

Maybe the joke is the lack of devops knowledge where Python is extra steps over other scripting languages?

It seems like promotion of fad languages. When I was younger, I chased fads and lost hard. I'll stick with C and C++. Run-time failures happen to everyone including fad languages. Here's looking at you Rust CVE's. Better to have loved and lost, something, something.

[–] elkien@lemmy.today 3 points 1 day ago

Plenty of complex things have been written in fad languages. And not only complex things, COBOL was one of the biggest fad languages of all time.

[–] echodot@feddit.uk 6 points 1 day ago (1 children)

I'm completely confused by why they seem to think it's impossible to have coding errors in rust. I'm also confused as to why they seem to think that errors are actually a problem. You get them you fix them. Who cares about what language you do it in.

This stinks of somebody who's been in the industry for about 2 years and now thinks they're hot shit.

[–] Tlaloc_Temporal@lemmy.ca 1 points 1 day ago (1 children)

If the language makes common but dofficult to deal with error impossible, that's nice. Not critical, but nice.

If the language introduces easy to make and hard to deal with errors, that's an issue. Not a deal breaker, but an issue.

The idea does exist, but it's stated with way more confidence and finality than it deserves. That's social media I guess.

[–] echodot@feddit.uk 1 points 18 hours ago

I still don't accept the fundamental core point of the arguement which is that rust necessarily makes it impossible to commit certain errors. Rust has its rules as such as only programming language does but that doesn't mean that mistakes are impossible.

The vast majority of errors are logic errors not memory leaks in standard functions.

[–] bleistift2@sopuli.xyz 55 points 2 days ago* (last edited 2 days ago) (18 children)

I agree with the post. Setting up typescript takes an hour or two if you have no clue what you’re doing. In return you get the absence of (the equivalent of) null pointer exceptions.

I chuckle every time I find an NPE in the Java backend. Doesn’t happen to me. Can’t happen to me.

Sidenote, while I’m already gloating: Once the backend code had an error where they were comparing two different kinds of IDs (think, user ID and SSN), which gave wrong results. This error can’t happen to me either, because I type my IDs such that they are not comparable. A strong type system really is a godsend.

load more comments (18 replies)
[–] Bane_Killgrind@lemmy.dbzer0.com 35 points 2 days ago (1 children)

Nonsense. If your code has reached the point of unmaintainable complexity, then blame the author, not the language.

I feel like there's about one person that can cast this stone, and that's because preventing this has turns Torvalds into an abusive bridge troll sometimes, but he's actually been successful.

load more comments (1 replies)
[–] wer2@lemmy.zip 11 points 2 days ago (2 children)

Sounds like they want Ada Spark and not Rust.

[–] tetris11@feddit.uk 1 points 1 day ago

Spark's syntax reminds me of submitting an application to a bank before I had a permanent address.

Yes it looks like I'm checking all the boxes, but I have to fudge some requirements just to get the process running, and remind myself to update the details later

[–] baines@lemmy.cafe 2 points 1 day ago

i laughed pretty hard thinking isn’t that just ada

so we got rid of ada for c++ now from c++ to rust chasing ada lmao

load more comments
view more: next ›