Ewww default exports. Explicit named exports are better! And so it begins
this post was submitted on 24 Sep 2023
510 points (92.9% liked)
Programmer Humor
32179 readers
422 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
How very dare you share my opinion!
PascalCase default exports for Classes
camelCase named exports for functions
ALL_CAPS named exports for constants
How about some fun?
How about some fn instead?
pub async fn foo() -> Pin>>>>>
oh fuck commonmark cant display the syntax :( well anyone who has done async rust can imagine
p a f fn(){}
load more comments
(2 replies)
these puns are getting funcy
Chef's kiss 👌
So much better
fun is the punchable face of keywords. I don't know why, but I hate it.
Oh, you're no fun.
^I'll see myself out.^
For me it's friend
I prefer good old def
How about some (defun)?
better than function
Kotlin?
Yes
load more comments
(1 replies)
Python is fine as a language I guess
But python programmers give it a bad name. I've never seen "well written" python code, it's always shit that's been thrown together cos it works.
I use python exclusively when I want to quickly throw some shit together that nobody's ever gonna spend any time maintaining, so that tracks.
When the grey beards wake up they're going to be fuming
Pfft! "Public static void main" is so jdk 20
int main() {}
Seriously. why isn't there any C love around here?
view more: next ›