Skip Navigation

Programmer Humor @programming.dev

alphacyberranger @lemmy.world

2y ago

Pick a side Javascript

41 comments

Jennifer is a lesbian. Her wife, now husband, who she’s proudly supportive of, is FtM, with 3 previous children that Jennifer adopted. Jennifer has never had penetrative sex with a man.
- Found the senior dev
- … checks out.
- interpreter programming language
- This would make her not a lesbian after her husband transitioned.
  
  Depends. Could be. A person transitioning doesn't necessitate their partner finding their new body attractive.

artificial insemination; beard marriage, loves her husband platonically. I am a JS dev.
- Lesbian, in marriage with another lesbian and adopted 3 kids. Still virgin.
  
  Her partner is actually a woman, but dynamic type casts made her write "husband".
  
  and by kids, she means their cats and/or dogs
- I was thinking they were his kids from the previous marriage, though artificial insemination works just as well!
- I've had a JavaScript certification for over a decade now and I think I hate you.
- Java devs are prima mental gymnasticists, always able to make anything make sense.
  
  JS !== Java
  Try Javascript some day!
  We have truthy and falsy! Empty string or null? Yeah, that's false!
  Of course we can parse a string to number, but if it's not a number it's NaN!
  null >= 0 is true!
  Assign a variable with =, test type equality with == and test actual equality with ===. You will NEVER use the wrong amount of = anywhere, trust me!
  Our default sort converts everything to string, then sorts by UTF-16 code. So yes, [1, 10, 3] is sorted and you are going to live with it.
  True + true = 2. You know I'm right.
  Try Javascript today!
  
  As a js dev, I will gymnastically take that as a compliment

Simple. Malformed data from.a bad actor. Always sanity check your shit.

If you have that much difficulty with JavaScript then it’s likely you’ll suffer with any language.
- Except strict equality, that's a JavaScript only problem. Imagine thinking "0" should be falsy in comparison due to string literal evaluation, but truthy with logical not applied based on non-empty string. Thus !"0"=="0" is true. They couldn't just throw away == and start over nooooo let's add === . Utter madness
  
  Browser compatibility. Design flaws can't easily be fixed like how other languages can just switch to a new major version and introduce breaking changes. ES must keep backwards compatibility so has had to do more additive changes than replacing behavior altogether so that older web pages pages don't break.
  
  Strict vs loose equality has gotten me so many times, but I can sort of see why they did it. The problem you mention with integers 0 & 1 is a major annoyance though. Like it is fairly common to check whether a variable is populated by using if (variable) {} - if the variable happens to be an integer, and that integer happens to be 0, loose quality will reflect that as false.
  But on the other side, there have been plenty of occasions where I'm expecting a boolean to come from somewhere and instead the data is passed as a text string. "true" == true but "true" !== true

NaN
- !NaN
  (Translation: I agree)

Any senior developer who says that should instantly get a demotion to intern.
- There are two kinds of simple
  Simple to learn to use
  Simple to understand, and use at a complex level.
  JavaScript is the first, but definitely not the second.
- Which part? Saying that it's simple, or making fun of saying that it's simple?
- Forced to develop on Windows

Hol' up

And I thought kotlin was crazy with whatever (modifier: Modifier = Modifier) means to make it happy

41 comments