No NullPointerExceptions in Kotlin.
this post was submitted on 08 Jun 2025
541 points (97.2% liked)
Programmer Humor
23955 readers
1241 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
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
Not a word of a lie, I saw a "segmentation fault" error in JavaScript.
Can't remember how we resolved it, but it did blow my mind.
Ive also seen this, but not from js but node
I find it funny that the pufferfish blows up at its own gunshot
Why is openbsd the referee?
Why is the crab not Rust. This is outrageous, it’s unfair
Rust would be some borrow checker compile error like
borrowed data escapes outside of associated function
argument requires that `'1` must outlive `'static`
rust errors are funny if you don't know rust
News at Ten: Borrowed Data Escapes Outside of Associated Function
Those also happen to be errors you'd typically run into, if you don't yet really know Rust...
Labelling the crab as C is sure to ruffle some exoskeletons..
As at least one nautically themed childrens' book surely has it: C is for crab.
Coming at programming sideways feels more like a Haskell or Prolog thing, though.
Apple is for ADA
Ball is for BASH
Crab is for C
Dog is for D
Elephant is for Ecsmascript
Fox is for F#
Goat is for Go
House is for Haskell
Igloo is for
...okay I got stuck there.
I mean, at the end of the day, if you really understand your language of choice, you know that it is jusf a bunch of fancy libraries and compiler tricks of top of C. So in my mind, I'm a fully evolved programmer in a language, when I could write anything I can write in that language in C instead.
only true if your language compiles to c. fortran peeps are safe.
I'm an 80's/90's BASIC bitch, so I'm still irrelevant!
10 PRINT "FARTS"
20 GOTO 10It's not what you can use that language to do - all general purpose languages are Turing Complete, so what you can do with them is exactly equal. It is about what the language will do for you. Rust compiler will stop you from writing memory unsafe code, C compiler cannot do that.
But how does the Rust compiler do that? What does it actually check? Could I write a compiler in C that does this check on a piece of Rust code?
C is so simplictic, that if I can write a piece of functionality in C, I must understand its inner workings fully. Not just how to use the feature, but how the feature works under the hood.
It is often pointless to actually implement the feature in C, since the feature already has a good implementation (see the Rust compiler for the memory safety). But understanding these features, and being able to mentally think about what it takes in C to implement them, is still helpfull for gaining an understanding of the feature.
...are Turing Complete, so what you can do with them is exactly equal.
But they're only equal in the Turing complete sense, which (iirc) says nothing about performance or timing.
I mean, yeah, most languages are turing complete.
Rust: Downloading 7390327 crates...
I feel like Rust would be some complaint from the compiler saying that some apparently unrelated struct can't be Send/Sync for some inscrutable reason. Or something about pinning a future.
C trying to take the shortest path to the goal.
Would probably have won (and broken the universe), if the referee didn't exist.
Python is being even smarter by trying to underflow the distance to the finish line.
Noob should've used PNPM
This implies that Javascript will get moving in the correct direction once it finishes installing dependencies, but it's just going to get fucked with incorrect behavior that doesn't even have the courtesy to throw an actual error.
"npm install" in particular is getting me.
and then there's ruby who didn't even qualify but still would have done better than the others.
"NPM install" isn't going to be the direct result of a race condition in JavaScript. And while I'm not familiar with Python, I'd guess that an "Indentation error" wouldn't be one either. A missing library or syntax error that's only discovered by executing a particular branch is still just a missing library or syntax error, not a race condition.
Also, while Node.js is popular, it isn't an integral part of JavaScript in the way that the other errors are integral to their respective languages.
none of these are race conditions, they're just runtime errors. python only parses code when it is about to run that block so you can absolutely get a crash from bad indentation.
in my experience, the js world's focus on developer ergonomics has absolutely yielded some insane situations where running an installed script has caused it to start downloading more dependencies. however, this has unfortunately started happening in python too lately.
NullPointerException can be related to a race condition.
it can also not be.
Python? That’s an embarrassed GAMBAS!