Ewww default exports. Explicit named exports are better! And so it begins
this post was submitted on 24 Sep 2023
470 points (92.9% liked)
Programmer Humor
32410 readers
1 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(){}
Pin<Box<dyn Future<Output=Result<AsyncResponseThatYouWillHaveToAwaitAgain<ActualResultType>, InscrutableErrorTypeThatDoesntImplementDisplay>> + Send + Sync + 'static + 20MillionMoreAutoTraits>>
Exactly, now we are talking
these puns are getting funcy
So much better
Chef's kiss 👌
How about some (defun)?
Kotlin?
Yes
When the grey beards wake up they're going to be fuming
int main() {}
Seriously. why isn't there any C love around here?
Who doesn’t use arrow functions?
Arrow functions should be used only for callbacks. I hate that people has started defining named functions with arrow functions in JS. Arrow functions are not hoisted and the ordering of your functions is going to get wonky, because you need to define all you functions first before composing them, when it should be the other way around. Start with the most high-level function which calls lower level functions.
I had this exact fight with my team several months ago, and lost to popular opinion since the rest of my team are either zoomers or indifferent.
I've reached the point that I cringe at the mention of arrow functions because so many people seem to always want to use arrow functions.
Like I'm looking up something on stack overflow and half the answers are arrow functions that are that way for no other reason than to use the fun little =>
sum(your_mom <- rep(69, 420))
R?
NaN
your_mom is undefined
It's being assigned and passed to sum at the same time. One of the many entertaining quirks of R.