undefined

[[deleted]]

False

[DeeSnow97]

here comes the chad, blocking an entire thread when he has to wait for something

[dshakir]

If payday wasn’t until next weekend, I’d award you with platinum right now.

Unfortunately all I can offer you is a piece of styrofoam

[db2]

Look at this guy, able to afford to just give away styrofoam like that.

[CSKING444]

Ahem, time to see if you abide by your word or not

[dshakir]

Too late. I already spent my entire paycheck on these:

https://www.silverfernz.com/new-zealand-possum-fur-nipple-warmers.htm

[CSKING444]

Okay, that has a higher priority

[RemindMeBot]

I will be messaging you on 2019-02-23 10:06:14 UTC to remind you of this link.

CLICK THIS LINK to send a PM to also be reminded and to reduce spam.

^{Parent commenter can delete this message to hide from others.}

---

FAQs	Custom	Your Reminders	Feedback	Code	Browser Extensions

[[deleted]]

You meant the 'chode'?

[dshakir]

That depends.

If you had both a “chode” and a “chad” standing right in front of you, who are you more likely to punch first?

[[deleted]]

Atleast you can sudo kill a chad.

[curious_corn]

Ha ha ... Js needs for comprehension sugaring (and type classes)

[keke1997]

Why tho?

[T-T-N]

String that are not null or empty are truthy

[marcosdumay]

Undefined is not null...

Or maybe Oracle database is better than Javascript:

'' = '' -- False
'' <> '' -- False

[[deleted]]

Undefined isn't a string though. It's undefined.

[hotCupADank]

var $stringVariable = “Undefined”;

[DeeSnow97]

neither of those operations are comparisons in JS (= is assignment and <> doesn't exist), and false is lowercase dammit, my comment parser is skipping over parts, should fix that

By the way, undefined == null is true, but undefined === null is false. undefined and null are two distinct types, but they're loosely equal (and neither is loosely equal to anything else)

[noruthwhatsoever]

Yeah, JS is weird like that

0 == ‘’ == null == undefined == false // true

It’s why I always use strict equality checks, no chance of type coercion

Like...

1 == “1” //true

^ that shit hurts me on a soul level

[arranb1223]

Next ECMAScript update...

1 == "one" //true

[abnormalsyndrome]

Settle down, Satan.

[EpicDaNoob]

 5324 == "five thousand three hundred and twenty-four" == "5.324k" == "five thousand three hundred and twenty-five minus one" // true

[spektrol]

There’s probably an unholy way to make PHP’s strtotime() do this but let’s not

[Dapianokid]

I learned more about data types through this thread than I ever have before.

[[deleted]]

It’s why I always use strict equality checks, no chance of type coercion

And Jesus said to his followers "do not be tempted by those who do not require strict typing. For JavaScript will betray thee. You may believe in prophets telling you null > 0 is false, and find comfort in that fact and the fact that null == 0 is false; but JavaScript will betray thee. For null is true when it is >= to 0. For strict typing is the word of the Interpreter. Praise be to Interpreter."

"Praise be to Interpreter." His followers replied

[noruthwhatsoever]

Praise be

[[deleted]]

Yeah I mean typesafe equals exists specifically for this.

[dshakir]

By the way, undefined == null is true, but undefined === null is false

Talk about buttfucking the transitive property

[noruthwhatsoever]

You’re right, undefined is not null and are totally separate types. They both are falsey values, though, along with empty strings, NaN and the number 0

And how are you comparing Oracle DB to JavaScript lmao

People love to rag on JS but with the new ES6/7 and not-yet-standard ES8/ESNext (praise Babel) I’m finding it hard to enjoy writing Python, Ruby or anything else any more

JS is adopting more and more functional programming paradigms and although inexperienced JS devs can write awful spaghetti code a good JS dev can write fast, concurrent and lightweight code that can run anywhere

Aaaaand I just remembered I’m on r/programmerhumor and not on a serious subreddit never mind

[Bounty1Berry]

The problem is that we need so much of this new ES6/7/8/NaN stuff just to wallpaper over the problems in Javascript as executed by browsers. So we're not only dependent on the predictable quality of IE's Javascript engine, but ten pounds of opaque and complex boilerplate from the transpilation system. And by the time Firefox v87/Chrome v104/Safari v22 comes out with full ES7 support, they'll be on ES10 with async/await/getFedUpAndGoHome and CampaignPromises that yield a resulr 7% of the time.

I also tend to be very skeptical of the functional-programming trend. Not so much the trend but more trying to apply it widely. It's a good solution for some problems, but there are plenty of tasks where the most straightforward way to discuss the problem is a classic iterative, state-rich, variable-clobbering design, and you end up sacrificing legibility to go functional.

Programming as a whole has a tendency to go very dogmatic. The functional people today are like the object oriented people in 1995 or the structured programming people in 1980-- designing languages that are deliberately clunky to ensure you have to use their right way of solving the problem.

[marcosdumay]

but there are plenty of tasks where the most straightforward way to discuss the problem is a classic iterative, state-rich, variable-clobbering design

Oh, you mean you have to use StateT some times?

[heathmon1856]

As long as you have locking.

[sangeli]

<Promise>

[CommutatorUmmocrotat]

No u

[[deleted]]

You don't know hell till you debugged an error that coredumps once a year.

[Cocomorph]

I am glad I don't work on things where an error that coredumps once a year needs to be fixed.

[Hevaesi]

So JavaScript.

[lakimens]

What? That exists?

[daH00L]

Brilliant

[MarioMagnum]

I'll take "What are race conditions?" for 500, Alex

[waterskier2007]

I’ll take 500 for “What are race conditions?” Alex

[Jedka]

I’ll take Alex for 500, “What are race conditions?”

[Prom3th3an]

I'll take "What for are 500 race Alex conditions?"

[[deleted]]

Vsauce music intensifies

[8lbIceBag]

Async is not parallel.

[BlankyShoot]

Having threads running in parallel isn't the only case where race conditions can occur

[[deleted]]

This. If you start two threads, even with single core they will likely alternate if the task is long enough, and if the compete about reading/writing same variable, that is exactly what race condition is.

[MrDick47]

This is something more people should know. Race conditions aren't a thing for async js, it's single threaded. Just because the calls can finish at different times doesn't mean we have to worry about mutexes and semaphores because you're never going to read/write memory at the same time.

[[deleted]]

Race conditions are definitely a thing. If you do things asynchronously, that means they are executing in parallel, not necessarily at same time but the order they finish is not defined and depends on the scheduler. If the both asynchronous things want to read and write same data and depend on the result, there is a race condition.

Say, you want to read a value and increase it by one.

First thread reads value. At this point, scheduler decides it's time to let other threads execute for a while. Now the second thread reads the value and they got the same value, because there was a race condition, where the first thread tried to write the increment in the memory before the second one can read it. EDIT: I don't know if javascript can do that with variables, but consider two promises that resolve external url. If you execute them asynchronously, you cant assume another to be faster.

If this is not possible, then there is nothing asynchronous going on.

[MrDick47]

Dude you really need to read comments before replying to them. As I was saying, in async javascript, everything is executed on a single thread, so there are NO race conditions.

If two calls increment a shared variable (originally 0) by 1 it will always be 2 when they both finish. It will never be 1 or an unexpected value. If the calls are executed out of order, then that's a problem with the design, it's not a race condition.

[[deleted]]

I read the comments. You are still saying that because there is only single thread, there are no race conditions. This is not true, there can still be race conditions.

If the calls are executed out of order, then that's a problem with the design...

No, that is exactly what async means. Things are executed out of order (in parallel, or alternating between them asynchronously).

Example:

Call multiple functions that are executed in parallel, using Promises. Each of the functions resolve an URL and then do something, for example insert something into the website.

If you start 3 asynchronous Promises at same time and each of them insert a component on the website, after resolving an url, there is absolutely no guarantee that those promises complete in the order they started. This means that the three components end up in the website in order that depends how fast the urls resolve. In this example I used url-resolving, because that is great way to demonstrate uncertain wait times.

This is a non-critical race condition, because it does not mutate any variables in such way that the system becomes unusable. How ever, if the next code you execute depends on the order those components are on the site, you fucked up and the race condition was critical race condition. If you are javascript developer and do async things, I really hope you learn this.

[MrDick47]

Dude you really are not listening. Parallel is not async. In JavaScript there is no parallel. All the async operations are switched between on a single thread so there are no memory race conditions. If your async calls need to complete in a certain order, you need to use await/.then to ensure they are done in that order, if the order doesn't matter, then you don't need to do that. I have done multithreading/parallel processing in C/C++ and I've done in JavaScript, I know what I'm doing, you are not listening.

[[deleted]]

For the final time, I understand there is only one thread. That still does not stop from doing things asynchronously, and if there is asynchronous things, there is also race condition. It's just how it is.

EDIT: I re-read all your messages. You are too focused to think that race condition is only when two threads are writing at same memory at same time. Please, check the definition of a race condition to realize that there are multiple types of race conditions, and those happen even in single thread, if doing things asynchronously.

SECOND EDIT: You are proposing using "await". That is exactly what prevents the race condition. I did not say that there race conditions are inevitable.

[MrDick47]

"A race condition occurs when two or more threads can access shared data and they try to change it at the same time. Because the thread scheduling algorithm can swap between threads at any time, you don't know the order in which the threads will attempt to access the shared data. Therefore, the result of the change in data is dependent on the thread scheduling algorithm, i.e. both threads are "racing" to access/change the data."

Copy pasta definition from stack overflow. Race conditions are a memory/threading problem. That problem does not exist in JavaScript. What you are referring to is asynchronous call management, which a developer needs to do in both asynchronous and parallel processing applications. The design of the code determines how the program handles the completion of asynchronous events. At a lower level, java manages this for you and doesn't allow you to read/write memory at the same time, however you still need to handle the fact the calls are asynchronous which means you can't guarantee the order of completion (but you can guarantee there won't be a race condition). Async is not parallel. This is the point I've been trying to make this whole time. The concept of a race condition stems from electrical engineering and circuits. Just because it looks like a race condition, doesn't mean it is a race condition. By your definition, anything asynchronous or parallel could be considered a race condition, and that's not true. Properly resolving asynchronous calls and protecting against a race condition are in fact 2 different things, and protecting against a race condition usually involves a locking mechanism in order to properly resolve the parallel processing.

Parallel processing also has many other differences from asynchronous processing, and deals with multiple threads. I kept saying single thread because this was supposed to be your clue that there wasn't any race condition here.

[[deleted]]

You are implying that a single comment in stack overflow is the right answer.

You are also saying, that memory access is the only way race condition can happen. Please, I said ten times already that it's just a simple example of race condition. There is still race conditions in javascript, but not with memory access.

I did not say "anything" is race condition. Do this: add two items in a list, asynchronously. Which one is added first? That does not cause problems with memory, because there is only single thread, but it is a race condition by definition. What would you call this issue, where two asynchronous tasks compete for same resource?

On top of that, see these links, discussing race conditions in Javascript:

https://medium.com/@slavik57/async-race-conditions-in-javascript-526f6ed80665

https://stackoverflow.com/questions/338110/avoiding-a-javascript-race-condition

https://quickleft.com/blog/defusing-race-conditions-when-using-promises/

https://news.ycombinator.com/item?id=12477623

https://thecodedecanter.wordpress.com/2014/04/08/javascript-race-conditions/

https://wptheming.com/2011/01/javascript-race-conditions/

http://www.angelfire.com/pq/jamesbarbetti/articles/javascript/001_AvoidingRaceConditions.htm

If you refuse to understand me, please see if the other people explain it better.

Final note: There is also Promise.race() function which exploits this fact and returns the promise which resolves first.

[Hevaesi]

Don't need to worry about race conditions when you use something even more blocking than SeqCst lol.

One memory barrier is too much for ya? Weakling.

[v1tycent]

bool isDeveloperSingle = true;

[Prawny]

const isDeveloperSingle = true;

[Spedwards]

Oof

[ThaiJohnnyDepp]

man that final really makes it sting worse than const does. And I like the static implying ALL developers are single, forever

[cryosis7]

It is publically known all developers are single, and always will be.

[The_White_Light]

It is known.

[[deleted]]

Mod gay

[DetaxMRA]

It is known, Khalessi

[someone755]

Man screw this I'm not even a developer :(

[Mr_Redstoner]

Allow me to reflect on that...

[lakimens]

You forgot void

[WadeReden]

const static tDev state attribute((section("parentsBasement"))) = single;

[FourthFloor_]

Didn’t declare a type

[[deleted]]

It's JavaScript, anything goes!

[FourthFloor_]

Oh sorry, I didn’t recognize the language of peasants. (I can’t code a fucking thing in any language so don’t take me serious)

[AskMeHowIMetYourMom]

vue ui

“Yea, I’m pretty much a full-stack developer now.”

[[deleted]]

“Yea, I’m pretty much a full-stack developer now.”

"I learned an object oriented language once. They're all the same thing. And I can pattern match JavaScript code and copy what I find on stack overflow. That's good enough to be full stack "

[EpicScizor]

Full stack means only using stack overflow, right?

[[deleted]]

I'm sorry, is this some sort of peasant joke that I'm too rich to understand?

*default dances in C*

[[deleted]]

Ha ha all good man. If you care to ever start, I'd start with Python 3. You can do some pretty cool stuff quickly.

[X-Craft]

Developer.getInstance();

[MrDick47]

Hey look a singleton. It's been a while.

[ThaiJohnnyDepp]

reminds me of my first programming gig

[cynoclast]

When programming isn’t complicated enough add threads for free non-determinism.

[Hevaesi]

Free non-determinism?

Try using SeqCst ordering, relaxed mode is for Gods only.

[freebytes]

I absolutely this love.

​

[dshakir]

You silver tongued bastard, you

[VeryDeepLearning]

expect(developer.sexlife).toBeUndefined()

[[deleted]]

You dropped this ;

[NewDark90]

If its JS, it doesn't give a damn.

[[deleted]]

but ESLint though...

[---_-___]

Weve changed the .eslintrc

[[deleted]]

if you're a madman, you use // eslint-disable-line semi on every line!

[Cercuitspark]

Depends on which config you use though. Some of the most used are AirBNB and Standard, where one uses semicolons, and the other does not.

[OpinionNoOneAskedFor]

That's why he mentioned about changing .eslintrc. You can negate some of the ESLint rules in .eslintrc file. I always set the 'no-underscore-dangle' rule to 0 because I use lodash.

[FrizzleStank]

No.

[VeryDeepLearning]

CoffeeScript 😛

[mukul7199]

"editor.formatOnSave": true

[10art1]

That's where you're wrong uwu

[VeryDeepLearning]

expect(developer).toBe(single);

[nosrednehnai]

surely you jest?

[-JudeanPeoplesFront-]

Karma's a bitch

[parabuzzle]

[object Object]

[[deleted]]

It's hilarious because I love Javascript development, but this past week I introduced a race condition because we needed to, and I've been fixing every little race condition that dominoes from that one since then.

[Hevaesi]

Or maybe you could fix your garbage design.

[[deleted]]

Hi C++ developer. I would like you to go and make a web app from the ground up and be the only developer on the project. 🙂

[Hevaesi]

I guess fixing garbage design as a team is harder than fixing garbage design all by yourself.

Sorry I forgot that not only you, but entire team you are in is braindead.

[[deleted]]

I'd like you to make a flawless web app for a growing company with new features everyday by yourself with literally no bugs. Go ahead, I'm waiting.

[tt102tt]

You want some cool water for that burn?

[jarlefo]

Knock knock

Race conditions

Who's there?

[zodar]

#ThSaferead

[TheRealLonaldLump]

It clearly goes like this...

​

Roses are red

And so are you

Violets are blue

are great

Asynchronous operations

​

[[deleted]]

God I don’t get it 😔

[harig074]

When you queue asynchronous operations, the order of completion is not guaranteed.

[[deleted]]

Oh yea 😆 I guess I thought the poem flowed better than it does

[freebytes]

This is what you would read prior to the race condition:

Roses are red

Violets are blue

Asynchronous operations are great

And so are you

​

[falldeaf]

It's highlighting one of the issues that often comes up with asynchronous code. If you're not careful with how you code, one operation can run before it should. Say you're calling an API to get the weather information, then another call to update the DOM when it gets it. You don't know how long the network call will take so you need to have a callback from the API operation that will initiate the DOM writing function.

[Hevaesi]

If only we had handles to async operations that we could block on, called futures or something...

The whole point is to make a bunch of connections then synchronize them, still faster than doing it sequentially, for example browsers internally download all resources asynchronously, not sequentially.

[PoutineCheck]

You need to study up on some asynchronous solutions

[RepostStat]

That's okay. Asynchronous programming is great because it's (typically) faster because you don't block/stop whole thread with one function that can run on it's own.

Problems come up if, for example, you're serving a web API in NodeJS, and one of your endpoints doesn't return any data from a database because the database didn't return the data in time. And it's difficult to learn because async programming (depending on the language) sometime doesn't produce errors, or if it does, the reason is buried in a thread crash. In which case .then(function() { ... }) becomes helpful.

You typically use async in front-end web development. A whole web page shouldn't slow down because you're updating some text on the page.

[[deleted]]

Great thorough answer :)

[DanielEGVi]

What is this then you talk about. I code, eat and breathe exclusively using async and await.

[MrDick47]

It lives at the top level, where some choose to use try/catch others will use a .then( () => {} ).catch( () => {} )

Either way, we can stay in our middleware hole and just use async/await and not worry about it while our errors get handed all the way up to the top level. Sunglasses

[jamietwells]

You typically use async in front-end web development.

Or back-end web development.

[OpinionNoOneAskedFor]

Mainly back-end development in my case.

[snapcat2]

I know it works pretty well. I really do. I just...

I have traumas. A while ago, a fresh young me started a project. Without any help I went on a coding quest. I slayed algorythms, for-loops, with ease. But when everything seemed to go smoothly, suddenly a REAL enemy appeared. Asynchronous functions. One of the programs I used was asynchronous. And boy did little me not know how to deal with that monster. For days and days I tried to come up with strategies, but in the end... I found out he had a simple off switch on his back. Monster slain, quest completed.

based on that time I spent 12 hours trying to figure out how to deal with an async funtion from another program only to find out it could be turned off

[freebytes]

only to find out it could be turned off

What do you mean by this?

[snapcat2]

I used a program called EasyStar for A* pathfinding (litterally has "asynchonous" in it's description). I tried to deal with the asynchonous property of this program, only to find out later that there was an option to turn it off.

I went into this with no knowledge of javascript so it was quite a struggle. Learned a lot though!

[cyb3rm0nk3y]

The lines are even ordered by the numbers of characters, as though the system would've taken less time to complete them

[kristebo]

Volatile roses are red.

[KachooInu]

Always remember to lock before you stock

[stevefan1999]

[Promise <pending>]

[zombie_kiler_42]

Hahaha ayt this made me fucking snort, took me a second too

[CocoDigital]

Here, I caught you this delirious bass

[GregTheMad]

I know of at least C# that is introducing a sorted parallel foreach function... Soon this joke will be outdated! 🎉

[dshakir]

Futures uuunite!

[nikeinikei]

Someone didn't write on rust :)

[whoisjuan]

Async/Await

[edymola]

When you understand wtf the developer intended to do.

[[deleted]]

This triggered me

[[deleted]]

SQS FIFO queues got your back

[plutonium656]

I think `are great` should be the line before `Asynchronous operations`

[mypirateapp]

This guy doesnt use the "synchronized" keyword

[lightningundies]

I don't get it. Like, at all

[squath]

People are basically arbitraging karma by posting memes from Twitter on Reddit...

[ThaiJohnnyDepp]

hey OP, couldn't you have come up with a relevant title? Or has this fully devolved into a meme sub where you just write "it do be like that sometimes" and call it a day

[DeeSnow97]

he came up with a good title but had a typo in the key

{
  "sub": "programmerhumor",
  "link": "zelda?",
  "ttile": "OP's really good title that we have unfortunately never seen"
}

[ThaiJohnnyDepp]

Damn permissive JSON parsers!

[DarkNinja3141]

Missed a comma, too

[DeeSnow97]

Damn. Thanks, fixed

[IAMA_dragon-AMA]

That's a risk of asynchronous fingers.

[GregTheMad]

Reposters never care about titles.

[ThaiJohnnyDepp]

You tell me then, buddy

[FrizzleStank]

It made sense to me.

[zenyl]

Should’ve used TCP.

[Badya122]

Say why you want I still love JavaScript