You must log in or register to comment.
My favorite, since I’m not a programmer anymore, is excel
E: Your formula has a circular reference. I ain’t doing shit till you fix it
Me: where?
E: In your spreadsheet, I don’t fucking know
Excel: taking ages to load a file
Excel: There is a link to another Excel document, but I can’t access it to update the value.
Me: Where?
Excel: To this document.
Me: … Where can I find the cell that contains this link?
Excel: I don’t know noises
Me: What if it is a named variable?
Excel: Yes.
And don’t even try to do a conversion of text to numbers in a big column. There’s a super fast way (name is eluding me) but if you respond to the error popup I imagine it looks at each cell of text, thinks says, “abracadabra you’re now a number!” for every row. It takes that long
It’s ok, you run the expression debugger, which says the first step, which is all of the formula, will result in an error. So helpful.
Sounds like Rust propaganda to me >:(
Tbf, you have to be pretty far with Rust to get to a point where Rust’s compiler errors stop helping you (at least, as far as I’ve seen). After that, it’s pretty much the same
Yep use a little bit more deeply cascaded generic rust code with a lot of fancy trait-bounds and error messages will explode and be similar as C++ (though to be fair they are still likely way more helpful than C++ template based error messages). Really hope that the compiler/error devs will improve in this area
deleted by creator
Would know, I’ve never had a runtime error in Rust /s
‘it should pretty much never segfault’ uh, isn’t that the entire point of Rust? Unless you’re counting failing a bounds check as a segfault
deleted by creator
MySQL: you have an error near here.
Me: What’s the error?
MySQL: It’s near here.
Me: You’re not going to tell me what the error is? Okay, near where? Here?
MySQL: warmer… warmer…
Oracle: You have this error in line 1
User: Hey, no, there isn’t anything to cause this error in line 1
Oracle: I’m telling you, it’s in line 1
User: Hum… How many lines are in my 10 lines query?
Oracle: 1
MySQL: you have an error around here
Me: that’s the entire query. If you aren’t going to tell me what the error is, can you at least narrow it down?
MySQL: … Stfu
C just shrugs and says “Seg Fault.”
“Shit happenned!”
Probably forgot a semicolon
This joke is never funny; Forgetting a semicolon in c results in compile time errors, not runtime errors
deleted by creator
The range those words induce is crazy
Yeah, but which one i cooler?
Rust because having a package manager is important.
Even C has a package manager
Bebop, he would just submit his code to the Shredder.
Shredder = /dev/null confirmed?
Well at least C++ definitely is far away from cool, you can imagine the rest…
But he has a purple mohawk!
deleted by creator
Clearly, you haven’t gcc & gdb…
I like how this depicts how rust is designed more top down and C++ is designed bottom up.
How compiler builders see peppa:
https://www.deviantart.com/ian-exe/art/Peppa-pig-front-face-743773121
I think these two pigs are the best comparison of rust and c++ I’ve ever seen. Also considering the aesthetics, it’s so accurate.
How compiler builders see peppa:
even number of nostrils
Missed opportunity.
Way too short to be a real C++ error. Needs a few more pages of template gibberish.
Syntax error: unmatched thing in thing from std::nonstd::__map<_Cyrillic, _$$$dollars>const basic_string< epic_mystery,mongoose_traits<char>, __default_alloc_<casual_Fridays = maybe>>(from James Mickens’ The Night Watch, highly recommended with his other essays: https://mickens.seas.harvard.edu/wisdom-james-mickens)
Template>, Outer>>>::static_wrapper, spirit::parser::lever>::fuck_you
LISP be like: “There is an error here in this wierd code I just generated and which you never saw before. Wanna hotfix it and try again?”
Then there’s Haskell that would remove (well, used to at some point) your source code file if you made any errors: https://gitlab.haskell.org/ghc/ghc/-/issues/163
The world’s angriest compiler.
Ever tried using typenum numerals in Rust? 😅
Try it and see the errors with something like
typenum::U500.Or deeply cascaded generic code with a lot of trait-bounds…
Clojure: hold my beer
Segmentation fault. :
Core obliterated.
deleted by creator
“Fuck you … or not. One day … or two … or every day. For certain, when you least expect it”
(C++ errors involving memory pointers)
One of the reasons i started learning rust was bc of how easy it is to get into it, or at least that’s how it felt for me. It wasn’t until a few months into consistently writing that I started to encounter things that I didn’t understand.
The good thing about Rust is that if you have no idea of any problem in your code, it very likely because your code is ok.
On C++ things are different.
