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
For some reason, this just sparked an ancient memory of the Geek Code, which was a sort of signature block you could append to your emails and online bios to show off how much of a geek you were in the geekiest fashion possible.
Goddamn I’m old.
As much as this hurts,
yeet;as an aliasthrow;is hilariousOf all the gen z lingo yeet is the best.
You can yoink that word from my cold, dead hands!
Funnily enough, that is a keyword in rust.
(it’s a placeholder to remove any bikeshedding)
Ugh. Just
its_giving rizz ratios vibe;No more needless nesting plz
I really really dig the fuckaround/findout. It paints the try/catch with a more dreadful undertone and reeks of mystery.
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.
I visualized “try” as watching a young child climb something that might be out of their comfort zone, so you’re letting them, but stay ready to “catch” them if something goes wrong. I suppose “throw” would be if they soiled themselves in their fall, you can throw them back into the arms of their loving parent for cleaning.
But fuck_around, find_out and yeet would be fantastic.
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.
As well as the
yeetkeyword, I’m really friggin’ diggin’ this. [modernisation required]#define yeet throw #define let const auto #define mut & #define skibidi exit(1)The future is now!
slowly steps back and returns to basic and z80 assembly
*Gen Z assembly
Everyones first language should be brainfuck CMV.
As if default keywords are the biggest deal-breaker.
Good thing I’m sticking with GDScript.
Big “you damn kids and your phones” vibes from this
Every generation is peddled two insane concepts:
When they are young, they are told that they have a weird bizarre vernacular which sounds stupid to everyone else.
Then when they are old, they are told young people have a weird bizarre vernacular which sounds stupid to everyone else.
Then you die.
Aliasing no_cap and cap to true and false…
I might have to steal that…
play_stupid_games { // ... } win_stupid_prizes(thePrize) { // ... }I always thought it was “prizes”
It is.
FAFO block passes better
That’s way better than my emoji based programming language.
I’m not so sure. Send a link.
Haven’t published it yet.
Here are comparisons:
⚖️
🐲
🐲⚖️
⚖️🐲
🚫🐲⚖️
Post the GitHub repo.
I will help you make this happen.
Sure! It doesn’t do anything yet, I just have a text file with how I’m intending to architect it.
It quite literally started
twofour (edit: I can’t keep track of time) days ago.I’ll configure a repo, stick this in a file, and push it. I’ll reply with another comment so you (and others) can look it up.
I’ve come up with some crazy stuff. Instead of something like “class” to indicate a class, it’s
🏫 Followed by the emoji name of the class like 🖼️📁. So it will need to be able to handle operators in the name it’s amazingly gross! Properties and methods will also be emoji names, like to get the 🖼️📁 “File Name” it would be 📁💳.
I was kind of being sarcastic. I haven’t written a compiler since I rode my dinosaur to college. Still it’s a funny idea. Could probably do it in C using a bunch of pound defines.
I was thinking Rust, but that works too.
Because then I could call the Language Spoons.
It would as uncomfortable to use as it is to watch Rusty Spoons
I’d take that
yeetinstead ofreturn…This is a better argument to adopt Rust than memory safety or even sane package management.
i hate it so fucking much
I fucking love it. Gen Z slang is so lighthearted and fun.
