668

submitted 1 year ago by alphacyberranger@lemmy.world to c/programmer_humor@programming.dev

41 comments fedilink hide all child comments

all 44 comments

sorted by: hot top controversial new old

[-] stevehobbes@lemmy.world 227 points 1 year ago* (last edited 1 year ago)

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.

[-] iAmTheTot@kbin.social 129 points 1 year ago

Found the senior dev

[-] LazaroFilm@lemmy.world 25 points 1 year ago

… checks out.

[-] unreachable@lemmy.my.id 11 points 1 year ago

interpreter programming language

[-] SpicyKetchup@lemmy.world -4 points 1 year ago

This would make her not a lesbian after her husband transitioned.

[-] morphballganon@lemmynsfw.com 24 points 1 year ago

Depends. Could be. A person transitioning doesn't necessitate their partner finding their new body attractive.

[-] SingularEye@lemmy.blahaj.zone 98 points 1 year ago

artificial insemination; beard marriage, loves her husband platonically. I am a JS dev.

[-] Kraivo@lemmy.world 33 points 1 year ago* (last edited 1 year ago)

Lesbian, in marriage with another lesbian and adopted 3 kids. Still virgin.

[-] where_am_i@sh.itjust.works 26 points 1 year ago

Her partner is actually a woman, but dynamic type casts made her write "husband".

[-] unreachable@lemmy.my.id 14 points 1 year ago

and by kids, she means their cats and/or dogs

[-] amanaftermidnight@lemmy.world 11 points 1 year ago

Ah yes, the fursons and furdaughters.

[-] colorado@programming.dev 11 points 1 year ago

We prefer the gender neutral fur baby in this household.

[-] pastaq@lemmy.ml 4 points 1 year ago

That's ageist.

[-] IGuessThisIsForNSFW@yiffit.net 9 points 1 year ago

I was thinking they were his kids from the previous marriage, though artificial insemination works just as well!

[-] scottywh@lemmy.world 1 points 1 year ago

I've had a JavaScript certification for over a decade now and I think I hate you.

[+] Comment105@lemm.ee -7 points 1 year ago

Java devs are prima mental gymnasticists, always able to make anything make sense.

[-] Konlanx@feddit.de 77 points 1 year ago* (last edited 1 year ago)

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!

[-] Durotar@lemmy.ml 14 points 1 year ago

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.

I'm not sure whether this is satire or not.

[-] Konlanx@feddit.de 58 points 1 year ago* (last edited 1 year ago)

It's not. The default sorter does that, because that way it can sort pretty much anything without breaking at runtime. You can overwrite it easily, though. For the example above you could simply do it like this:

[3, 1, 10].sort((a, b) => a - b)

Returns: [1, 3, 10]

[-] newIdentity@sh.itjust.works 5 points 1 year ago

Holy shit that's actually true. I just tried it

[-] sociablefish@programming.dev 2 points 1 year ago

The default sorter does that, because that way it can sort pretty much anything without breaking at runtime.

who the fuck decided that not breaking at runtime was more important than making sense?

this js example of [1, 3, 10].sort() vs [1, 3, 10].sort((a, b) => a - b) will be my go to example of why good defaults are important

[-] sociablefish@programming.dev 1 points 1 year ago

who uses utf 16? people either use utf 8 (for files) or utf 32 (for string class O(1) random access)

[-] Beanie@programming.dev 1 points 1 year ago

True + true = 2. I've heard memes about Javascript, but jeez. It's really that bad?

[-] Comment105@lemm.ee 1 points 1 year ago* (last edited 1 year ago)

I made the thing in the thing print "hello world" with C# once, is Javascript for me?

[-] SouthernCanadian@sh.itjust.works 1 points 1 year ago

As a js dev, I will gymnastically take that as a compliment

[-] Blamemeta@lemm.ee 22 points 1 year ago

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

[-] Coreidan@lemmy.world 16 points 1 year ago

If you have that much difficulty with JavaScript then it’s likely you’ll suffer with any language.

[-] MakeAvoy@programming.dev 5 points 1 year ago

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

[-] soloner@lemmy.world 4 points 1 year ago

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.

[-] MyNameIsIgglePiggle@sh.itjust.works 7 points 1 year ago

Meanwhile google is about to break the internet with html drm

[-] JonEFive@midwest.social 1 points 1 year ago

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

[-] MakeAvoy@programming.dev 3 points 1 year ago

Lua does intrinsic evaluation of strings that i'd argue is not nearly as crazy. I get the value of it since half of interpreted languages it just churning through strings. But I also don't recommend any large codebase ever use JS's == or string coercion because it can go against expectations. This graph argues in JS's favor but comparison is a little more crazy https://algassert.com/visualization/2014/03/27/Better-JS-Equality-Table.html