Now I wanna see this in jive
Ah, yes. A private method for working on a public field.
Ah but maybe the vibe is a
lowkey periodwe can’t be sure
And a decade or so ago it was LOLCODE that had me mildly concerned for the wellbeing of my peers.
HAI 1.2 CAN HAS STDIO? IM IN YR LOOP UPPIN YR VAR TIL BOTH SAEM VAR AN 10 VISIBLE SUM OF VAR AN 1 IM OUTTA YR LOOP KTHXBYEA perfectly reasonable language. None of this Gen Z rubbish.
Something something better times. Shakes stick at sky.
Kids today just don’t know real code
My 21 year old is pretty into rust and html. Does that count?
I’m pretty ignorant on most of it. In my youth, I just dabbled trying to lean basic on a c64 and AMOS on the Amiga though, so maybe not lol
e: I think I missed the joke, probably because I’m old lol
Hell, kids today don’t even number their lines anymore. What’s wrong with the world?
Wow, hadn’t thought of that thing in ages. Now all we need is for B1FF to bring back ASCII sword signatures.
Remember it spawning a bunch of copycats? For a while every community had their own code block. I wrote one for a usenet group i was in at the time.
alt.sysadmin and alt.sysadmin.recovery both had em iirc…
deleted by creator
It’s so painfully good.
slowly steps back and returns to basic and z80 assembly
*Gen Z assembly
*z18 assembly
Too many capital letters in the gen z version.
That’s what we Do.
I really really dig the fuckaround/findout. It paints the try/catch with a more dreadful undertone and reeks of mystery.
As well as the
yeetkeyword, I’m really friggin’ diggin’ this. [modernisation required]Oh yes, this one too of course!
#define yeet throw #define let const auto #define mut & #define skibidi exit(1)The future is now!
just what you want from code !
Exactly!
Yeah, I love that one.
“Try” is too hopeful. “fuck_around” makes it clear that you know what you’re doing is dangerous but you’re going to do it anyhow. I know that in some languages wrapping a lot of code in exception blocks is the norm, but I don’t like that. I think it should be something you only use rarely, and when you do it’s because you know you’re doing something that’s not safe in some way.
“Catch” has never satisfied me. I mean, I know what it does, but it doesn’t seem to relate to “try”. Really, if “try” doesn’t succeed, the corresponding block should be “fail”. But, then you’d have the confusion of a block named “fail”, which isn’t ideal. But “find_out” pairs perfectly with “fuck_around” and makes it clear that if you got there it’s because something went wrong.
I also like “yeet”. Partly it’s fun for comedic value. But, it’s also good because “throw” feels like a casual game of catch in the park. “Yeet” feels more like it’s out of control, if you hit a “throw” your code isn’t carefully handing off its state, it’s hitting the eject button and hoping for the best. You hope there’s an exception handler higher up the stack that will do the right thing, but it also might just bubble all the way up to the top and spit out a nasty exception for the user.
The whole thing was pretty damn good all the way through. The only thing that had me wondering was
TeaUntil it got to
SpillTeaWell played.
NGL, that helped me actually understand the original function. It’s been over a decade since I’ve touched anything related to C.
Indeed. I was unfair of me to pick only one favourite, as there are more candidates :)
the suspense!
😂
(ノಠ益ಠ)ノ彡┻━┻
This was by far the best way to explain current slang.
I got all of it No TeaGood thing I’m sticking with GDScript.
Why does the bool have brackets? I haven’t really used c#, seems odd
It’s a method definition. C#'s standard formatting puts the left
bracketbrace of the method body on a new line. It’s equivalent to:private bool IsSus(){ ... }Ahhh, that makes way more sense. Thanks
I’ve seen forms of this joke quite a lot in the last few years, and it never fails to make me laugh.
As if default keywords are the biggest deal-breaker.
