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.
Only those who lack a sense of humor.
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.
So it’s just JS with an even more immature spec
I would disagree. Especially since unlike npm every part of cargo was through through with all the experience and knowledge gained from npm, pip, nuget & co.
I have a LOT more problems with npm over cargo. Also it’s 1 tool and not 100 different tools to do the same job (npm, pnpm, yarn, bun, deno, etc…)
Rust and Cargo were built to be in a symbiosis with each other.
NPM is an afterthought of a rushed language.
Rust is still in the locker room having an argument with their coach (borrow checker).
C++ is home sick, currently the doctor (compiler) is not sure whether it’s got the flu or a terminal cancer.
terminal cancer
“I’m sorry, you’ve been diagnosed with :():;:”
“You have a couple seconds to live.”
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 functionargument requires that `'1` must outlive `'static`rust errors are funny if you don’t know rust
Those also happen to be errors you’d typically run into, if you don’t yet really know Rust…
I do run into them even though I use Rust for ~3 years now, but only in non-obvious cases, e. g. when all references to the borrowed data are dropped before the end of the function.
you can still segfault in rust iirc
Not in safe Rust. Only if you explicitly tell the compiler “I got this, don’t worry” but then fuck up.
I guess they fixed the weirdness involving calling main later in the program
As in, you call
main()recursively? Don’t think, I’ve ever tried that in any language…
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.
Technically any language runtime can end in a segmentation fault.
For some languages, in principle this shouldn’t be possible, but the runtimes can have bugs and/or you are calling libraries that do some native code at some point.
Even safe rust can do it, if we allow compiler bugs
Ive also seen this, but not from js but node
I have seen a Java program I wrote terminate with SIGSEGV. I think a library was causing it.
“npm install” in particular is getting me.
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.
incorrect behavior that doesn’t even have the courtesy to throw an actual error.
To be fair, this can be said of C. A C executable only really forces a crash out when you royally screw up beyond the bounds of your memory. Otherwise functions just return a negative value and calling code that never bothers to check just keep on going.
Golang is similar, slightly mitigated that if you are assigning any return value from a function, you must also explicitly receive an error and you know full well that you are being lazy if you don’t handle it. Well unless you use a panic/recover scheme but golang community will skewer you alive for casually suggesting that and certainly third party libraries aren’t going to do it that way.
Why is openbsd the referee?
The puffer fish is Bash
Yep, it’s the one starting everything.
And doing nothing else. And still something manages to no be right.
I find it funny that the pufferfish blows up at its own gunshot
Rust isn’t shown because it’s already completed the course
“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.
Correct
I had to come up with a title, this was it.
It’s a cartoon.
Removed by mod
No NullPointerExceptions in Kotlin.
The humble
!!operator.Well, also the fact that all variables are non-nullable by default anyway.
Python? That’s an embarrassed GAMBAS!
