- Knock, knock

- An async function

- Who's there?

Yoda speaks like he wasn't careful with his async calls

"a Jedi You are"

5 things you will find shocking about asynchronous code:

3.
2.
5.
1.
4.

STOP👏MAKING👏ASYNC👏CALLS👏FREEZE👏THE👏GUI👏THAT👏IS👏THE👏POINT👏OF👏ASYNC👏

"Maybe" is just an async "No"

10 Things You’ll Find Shocking About Asynchronous Operations:

3.
2.
7.
4.
6.
1.
9.
10.
5.
8.

(found on twitter by @iamdevloper 😂)

That WTF moment before you realise the code is asynchronous...

Still awaiting my async enlightenment 😝

Async/await, welcome to the family of JavaScript😀

At my old company one of my colleagues introduced async / await into our csharp code. He created interfaces and showed us a great structuring of his code. Sadly a few weeks later he left the company, because of personal reasons and a bug appeared in his written service. Our senior developer took the issue and complained for like 1 week. That you can't find anything, that interfaces are useless, that async / await is slow and sucks and that we should stop trying to bring new structures into the code base and do things the old way. In the end he deleted all the great things that my colleague introduced and wrote bad and smelly code.

When you get used to async web programming and then come back to desktop java/c#. Oof.

You lose your virginity as a dev when you first try async programming.

!Story

The day I became the 400 pound Chinese hacker 4chan.

I built this front-end solution for a client (but behind a back end login), and we get on the line with some fancy European team who will handle penetration testing for the client as we are nearing dev completion.

They seem... pretty confident in themselves, and pretty disrespectful to the LAMP environment, and make the client worry even though it's behind a login the project is still vulnerable. No idea why the client hired an uppity .NET house to test a LAMP app. I don't even bother asking these questions anymore...

And worse, they insist we allow them to scrape for vulnerabilities BEHIND the server side login. As though a user was already compromised.

So, I know I want to fuck with them. and I sit around and smoke some weed and just let this issue marinate around in my crazy ass brain for a bit. Trying to think of a way I can obfuscate all this localStorage and what it's doing... And then, inspiration strikes.

I know this library for compressing JSON. I only use it when localStorage space gets tight, and this project was only storing a few k to localStorage... so compression was unnecessary, but what the hell. Problem: it would be obvious from exposed source that it was being called.

After a little more thought, I decide to override the addslashes and stripslashes functions and to do the compression/decompression from within those overrides.

I then minify the whole thing and stash it in the minified jquery file.

So, what LOOKS from exposed client side code to be a simple addslashes ends up compressing the JSON before putting it in localStorage. And what LOOKS like a stripslashes decompresses.

Now, the compression does some bit math that frankly is over my head, but the practical result is if you output the data compressed, it looks like mandarin and random characters. As a result, everything that can be seen in dev tools looks like the image.

So we GIVE the penetration team login credentials... they log in and start trying to crack it.

I sit and wait. Grinning as fuck.

Not even an hour goes by and they call an emergency meeting. I can barely contain laughter.

We get my PM and me and then several guys from their team on the line. They share screen and show the dev tools.

"We think you may have been compromised by a Chinese hacker!"

I mute and then die my ass off. Holy shit this is maybe the best thing I've ever done.

My PM, who has seen me use the JSON compression technique before and knows exactly whats up starts telling them about it so they don't freak out. And finally I unmute and manage a, "Guys... I'm standing right here." between gasped laughter.

If only it was more common to use video in these calls because I WISH I could have seen their faces.

Anyway, they calmed their attitude down, we told them how to decompress the localStorage, and then they still didn't find jack shit because i'm a fucking badass and even after we gave them keys to the login and gave them keys to my secret localStorage it only led to AWS Cognito protected async calls.

Anyway, that's the story of how I became a "Chinese hacker" and made a room full of penetration testers look like morons with a (reasonably) simple JS trick.

Girl you must be asynchronous, cause I'm always calling back.

async functions, the easy way

How my keyboard evolves:

0. Like any normal man, I started with a cheap standard Qwerty keyboard. As I began learning programming, I wanted something more elegant, so...

1. I've been using layout Dvorak (and then Programmer Dvorak) for like 5 years+ now. Anyone has intention to type on my machine soon gives up or even is blocked by me from the very start. It always takes a couple of minutes to explain to them what's going on here. They think I'm weird. I feel untouchable :)

2. My first mechkey was a 104-key Filco. Time flew by and I wanted my thing to be more compact so I went for a 66% and a TKL.

3. Recently I find out that though my keyboard is not a full-sized, there're yet some keys I've never touched (the bottom right modifiers, scroll lock, etc), so I look for a leaner one: HHKB and its alike but with slight remappings. Now I'm satisfied with the tiny, corners-trimmed keyboard but others look at it and ask how it is even possible to scroll the web page using the thing.

Prob 1: my boss can never type on my keyboard. Sometimes he still grumbles when he cannot correct my fouls right on my machine.

Prob 2: my keyboards at home and at work are not the same and some keymapping cannot applied to one of the two. That's async.

Dear javascript, you think you're sooooo fucking special. You just HAD to be asynchronous everywhere, losing all connections to natural sequential human thinking. I just want to work with the result of A GOD DAMN FOR LOOP you ASYNC FUCK.

When I write async code in ES7, I'm tempted to call my promises "chtulu", "messiah", "lastJudgement", etc.

async function doStuff() {
chtulu = someAsyncTask();
await chtulu;
}

Books and command lines.

I don't like teachers.

I think it's because my learning process is very async and chaotic. When I see a snippet in Golang, I relate it to PHP, Rust and Haskell. I jump to resolving the problem in other languages, trying to find out which approaches work in Go.

Then I read about some computer science concept on Wikipedia and get lost in that while my hunger for knowledge and food increases. After a while I look up a recipe for a pasta salad, and while cutting bell peppers, I see the recipe in terms of typed morphisms, I sprinkle and intersperse ingredients through mapping functions, then decide to write an interpreter for the esoteric "Chef" language in Go so I can interpret my salad recipe while eating it.

Voila, I'm learning Go.

I have no patience for linear mentoring, and others have no patience for mentoring me.

But that's OK.

Found my most ridiculous function ever, back from when I was first learning.

async Task Delay(int time)
{
await Task.Delay(time)
}

"We should use ambiguity-driven development using co-domain model sockets, anfractuous horizontal scaling, and recursive async testing"

"What even is that"

"I found some words I like in the dictionary, and used it as the title for a medium article. I thought that's how we play the game as devs these days"

Update on UWP File explorer! Exciting stuff first!

Reveal style was applied to the home page grid (That thing in WinX where the borders change color in proximity to the mouse)

Clickable buttons in the title bar! This is the first step to tabs!

Converted a lot of things that were generated dynamically in C# to UserControls in XAML, for easier reading and even improved code-behind options.

Pulled my hair out getting rid of System.IO - System.IO is not made for UWP and stops working in certain situations. Now using Windows.Storage, which is a lot more async. I have gotten much friendlier with the dispatcher.

Pain from the operation is really fading and school doesn't start for a couple days, so I hope to get a beta out before school starts, and more realistically, get the tab system done before school starts.

"Never do yesterday, what should be done tomorrow!"
- An async function

Modern web frontend is giving me a huge headache...

Gazillion frameworks, css preprocessors, transpilers, task runners, webpack, state management, templating, Rxjs, vector graphics,async,promises, es6,es7,babel,uglifying,minifying,beautifying,modules,dependecy injection....

All this for programming apps that happen to run inside browsers on a protocol which was designed to display simple text pages...

This is insanity. It cannot go on like this for long. I pray for webasm and elm to rescue me from this chaos.

I work now as a fullstack dev as my first job but my next job is definitely going to be backend/native stuff for desktop or mobile. It seems those areas are much less crazy.

This year's golden hammer at my company: async

If langs/platforms were pokemon

Nodejs i choose u
Nodejs uses async attack

Your turn

First rant: but I'm so triggered and everyone needs a break from all the EU and PC rants.

It's time to defend JavaScript. That's right, the best frikin language in the universe.

Features:
incredible async code (await/async)
universal support on almost everything connected to the internet
runs on almost all platforms including natively
dynamically interpreted but also internally compiled (like Perl)
gave birth to JSON (you're welcome ppl who remember that the X in AJAX stood for XML)

All these people ranting about JS don't understand that JS isn't frikin magic. It does what it needs to do well.

If you're using it for compute-heavy machine learning, or to maintain a 100k LOC project without Typescript, then why'd you shoot yourself in the foot?

As a proud JS developer I gotta scroll through all these posts gushing over the other languages. Why does nobody rant about using Python for bitcoin mining or Erlang to create a media player?

Cuz if you use the wrong tool for the right job, it's of course gonna blow up in your face.

For example, there was a post claiming JS developers were "scared" of multithreading and only stick in their comfort zone. Like WTF when NodeJS came out everything was multithreaded. It took some brave developers to step out of the comfort zone to embrace the event loop.

For a web app, things like PHP and Node should only be doing light transforms between the database information and HTML anyways. You get one thread to handle the server because you're keeping other threads open to interface with databases and the filesystem. The Nexus.js dev ranting on all us JS devs and doesn't realize that nobody's actual web server is CPU bound because of writing HTML bodies, thats why we only use 1 thread. We use other worker threads to do the heavy lifting (yes there is a C++ bridge look it up)

Anyways TL;DR plz respect JS developers we're people too. ES7 is magic and please don't shit on ES3 or we'll start shitting on the Python 2-3 conversion (need to maintain an outdated binary just cuz people leave out ()'s in their print statements)

Or at least agree that VB.NET is an abomination and insult to the beauty that is TI-84 BASIC

Debugging async multithreaded apps is so much fun that I have a pile of hair on my desk that's been pulled out in frustration.

Considering making a wig to wear after I'm done.

I think I'm finally getting async/await

JavaScript Motherfucking Asynchronous Bullshit.

I get it, for quite some stuff, async is very, very useful. But why on fucking earth do so goddamn many functions NEED this (and those callback functions) and can't do without?!

If there would be good and nicely understandable await documentation that actually fucking works, I'd be so happy.

I've currently got .then after .then after motherfucking then and its irritating me to no end as it, in this context, shouldn't even be necessary. This thing I'm writing doesn't give a fuck if something takes a few milliseconds before the rest of the program can continue!!

Fuck asynchronous programming in JavaScript for goddamn everything.

(I do love JavaScript!)

Did you fucking idiots think that I was gonna tell you to implement async await on the requests and not notice that you IMPLWMENTED GODDAMN SYSTEM-SLEEP YOU DESNE MOTHERFUCKEDS IT NOT TAKES 10X AS LONG AS MY OATCH TO JUST LIMIT THE NUMBER IF HTTP REQUESTS FOR FUCJS SAKE THIS CODE LOONS LIKE A RACCOON FUCKED AN MACBOOK THAT ALSO GOT FUCKED BY A GOAT FROM CHERNOBYL THAT SOMEHOW MUTATED TO A RACCOON GOAT 🐐 MACBOOK 💻 HYBRID ABOMINATION THAT IS NOW CLAWING MY EYES OUT AND GIVING ME RABIESCANCERAIDS

I've been using microsoft dev stack for as long as i remember. Since I picked up C#/.NET in 2002 I haven't looked back. I got spoiled by things like type safety, generics, LINQ and its functional twist on C#, await/async, and Visual Studio, the best IDE one could ask for.

Over the past few years though, I've seen the rise of many competing open source stacks that get many things right, e.g. command line tooling, package management, CI, CD, containerization, and Linux friendliness. In general many of those frameworks are more Mac friendly than Windows. Microsoft started sobering up to this fact and started open sourcing its frameworks and tools, and generally being more Mac/Linux friendly, but I think that, first, it's a bit too late, and second, it's not mature yet; not even comparable to what you get on VS + Windows.

More recently I switched jobs and I'm mainly using Mac, Python, and some Java. I've also used node in a couple of small projects. My feeling: even though I may be resisting change, I genuinely feel that C# is a better designed language than Java, and I feel that static type languages are far superior to dynamic ones, especially on large projects with large number of developers. I get that dynamic languages gives you a productivity boost, and they make you feel liberated, but most of the time I feel that this productivity is lost when you have to compensate for type safety with more unit tests that would not be necessary in a static type language, also you tend to get subtle bugs that are only manifested at runtime.

So I'm really torn: enjoy world class development platform and language, but sacrifice large ecosystem of open source tools and practices that get the devops culture; or be content with less polished frameworks/languages but much larger community that gets how apps should be built, deployed, monitored, etc.

Damn you Microsoft for coming late to the open source party.

What features would you want in a logger?

Here's what I'm planning so far:
- Tagged entries for easy scanning of log file
- Support for indenting to group similar sequential entries
- Multiple entry types (normal, info, event, warning, error, fatal, debug, verbose)
- Meta entries, so the logger logging about itself, e.g. disk i/o failures.
- Ability to add custom entry types, including tag, log-level, etc.
- Customizable timestamp function
- Support for JS's async nature -- this equates to passing a unique key per 'thread'; the logger will re-write all the parent blocks for context, if necessary. if that sounds confusing, it's okay; just trust that it makes sense.
- Caching, retries, etc. in the event of disk i/o issues.
- Support for custom writers, allowing you to e.g. write logs to an API rather than console or disk.

How about these features?
- Multiple (named) logs with separate writers (console, disk, etc.)
- Ability to individually enable/disable writing of specific entry types. (want verbose but not info? sure thing, weirdo!)
- Multiple writers per log. Combined with the above, this would allow you to write specific entry types (e.g. error, warning, fatal) to stderr instead of stdout, or to different apis.
- Ability to write the same log entry to multiple logs simultaneously

What do you think of these features?
What other features would you want?
I'm open to suggestions!

So I'm working on an CLI right now that fetches data from a website and downloads other stuff based on that data etc bla bla. And since its async it can fully taste my whole internet speed (130Mb/s).

So everything's good and I started working on a new feature. I started the app and it worked... For 3 minutes. After that it just stopped. It didn't even freeze or anything. After 2 hours of debugging and 3 cans of coffee I was so frustrated I just wanted to watch some YouTube and relax. That's the moment I realized I didn't even have internet. I hate my ISP...

When I was about 10 I tried to make a basic midi sequencer/synthesiser using just the python standard library.
The only sound production there was was winsound.beep, which played a sine wave at the frequency given.
I realised that if I put enough really short beeps together I could make some mildly convincing instruments - I remember an electric piano, acoustic guitar, some kind of bass synth, and maybe more?
Then I put them together to make a song. The problem was though that you can't play multiple notes together as winsound.beep was blocking (though I didn't understand that at the time).
I had no knowledge of threading or async so I opened multiple python interpreter instances to play multiple channels. That's how I learnt about command-line arguments!
But I really struggled to get the sounds to be in time because python is not exactly rapid.
I made a kind of note sequencer using a library called easygui, based on tkinter (TCL wrapper), and I remember being told off at school for bringing in a usb stick with the exe of my program that I made with py2exe.
So many old technologies and fond memories...

Ooh, look! Node got async/await!
Ooh, look! I can lint shell scripts with shellcheck!
Ooh, look! Webpack 2 has been released!
Ooh, look! I can switch over from npm to yarn!

There is so much stuff I want to upgrade and optimize in our project, that I forget about the actual JIRA ticket.

this is why you should learn async when learning a programming lang

Async/await my ass!

A co-worker doesn't like to use async/await operators, so he's always changing the code to use promises and callbacks and apparently async functions whitout awaits...

Building a wheel is great.
Building a steering wheel is also great
Building a brakes pedal is amazing.

Making them work asynchronously - not that good of an idea is it...

Who the fuck thought separating data stream (copying bytes) from stream control (when does the stream start/end) is a good idea...?

- open a connection
- send data to the stream
- send() returns
- close the connection

Apparently, the send() does not copy the data and returns. Instead, it enqueues the data copying task end returns. When does the actual copying start? IDK. When does it end? IDK. Can I close the conn? NO!

This thing is UNUSABLE. And I'd riddle it with reflection-based workarounds if it weren't for the static methods.

Fuck!

If you didn't think NodeJS dependency hell was that bad, you should try sequentially parsing a graph that's stored as an array of nodes and their references, where processing of said nodes forces you to use some async functions that depend on other async functions.

What should have been 20 lines of code written in 30 minutes has turned into 3 hours of horror, reading about babel, realizing that it's just adding more problems without solving one, assessing the effort of modification of async libraries to include sync methods as well, trying out asyncwait, async, and everything else there is, trying to rethink the recursive algorithm, rewriting it several times, cursing and hating myself for not choosing to use Python or .NET Core, screaming senselessly at my wife in a language as familiar to her as Klingon, crying in the bathroom, re-assessing my life choices, thinking whether it was a mistake to dedicate 10 years to this career, maybe I'm just not cut out for it since I can't handle this simple task, watching noose tying tutorials on youtube, thinking about my naked empty RPI that won't connect to the server any time soon.

Seriously. Why is it SO BAD?! Or is it just me?

Wanna hear a story? The consultancy firm I work for has been hired to work on a WPF project for a big Fashion Industry giant.

We are talking of their most important project yet, the ones the "buyers" use to order them their products globally, for each of the retail stores this Fashion giant has around the world. Do you want to know what I found? Wel, come my sweet summer child.

DB: not even a single foreign key. Impossibile to understand without any priopr working experience on the application. Six "quantity" tables to keep aligned with values that will dictate the quantities to be sent to production (we are talking SKUs here: shoes, bags..)

BE: autogenerated controllers using T4 templates. Inputs directly serialized in headers. Async logging (i.e. await Logger.Error(ex)). Entities returned as response to the front end, no DTOs whatsoever.

WPF: riddled with code behind and third party components (dev express) and Business Logic that should belong to the Business Layer. No real api client, just a highly customized "Rest Helper". No error reporting or dealing with exceptions. Multiple endpoints call to get data that would be combined into one single model which happens to be the one needed by the UI. No save function: a timer checks the components for changes and autosaves them every x seconds. Saving for the most critical part occurring when switching cells or rows, often resulting in race conditions at DB level.

What do you think of this piece of shit?

I've been working on a proof of concept for my thesis for a few days and the async query calls drove me nuts for quite a while. I finally managed to deliver all query results asynchronously while still very much relying on a strong architectural design pattern. I am filled with caffeine, joy and a sense of pride and accomplishment.

It was the first time I worked on a big project with a big team, I looked at the given code and copied their code style.

I finished very fast and everything was working fine, was really proud of myself. I'd like to add some logging though.

Programm failed it was heavily async and parallel so 2 days of debugging had past the whole team was on board nobody knew what went wrong there.

As I stared into the darkness of my code I suddenly saw what went wrong 😂

As I adopted no curly braces style of the Team for

If (condition)
Justine();

And I added logging above without braces everything broke 😂 it was indented properly so as a heavily python user everything looked fine

its problems. tricky Async has

I'm not much a fan of JavaScript. In fact, I am not very fond of any dynamic language, but JavaScript is one of my least favorites.

But this isn't about that. I use NodeJS for all of my web serving. Why would I do that? Am I a masochist? Yes.

But this isn't about that. I use NodeJS because having the same language on client and server side is something that web has never really seen before, not in this scale. Something I really really love with NodeJS is socket connections. There's no JSON parsing, no annoying conversion of data types. You can get network data and use it AS IS. If you transmit over socket using JSON, as soon as that data arrives on the server, it is available to use. It gets me so hard.

JavaScript is built to be single-threaded, and this is rooted deep into the language. NodeJS knows this isn't gonna work. And while there's still no way to multi-thread, they still try their best and allow certain operations (Usually IO) to run async as if you were using ajax.

With modern versions of the language, the server and client side can share scripts! With the inclusion of the import keyword, for the first time I have ever seen, client and server can use the same fucking code. That is mindblowing.

Syntax is still fluffy and data types are still mushy but the ability to use the same language on both sides is respectable. Can't wait for WebASM to go mainstream and open this opportunity up to more languages!

Back in the day, when callbacks was all I've found on Internet tutorials, my code looked like this (img) . But then I found something called "async" and it changed my life!

But I couldn't let go of my old ways, so the code with async looked just like the callback one, but with new boilerplate code.

The thing is: you can't simply USE something new like you were using the old one. you'll probably use it wrong. you have to understand that this new thing is different and adapt your thinking process to better work with it.

you can sit on a skateboard and go forward using your hands on the ground to push it, but that's not how it was designed to work.

I still use callbacks because I have no intention of rewriting my working codebases right now (because they work just fine). But, even with my struggles in changing to new tech, I've learned to adapt (sort of).

As a pretty solid Angular dev getting thrown a react project over the fence by his PM I can say:

FUCK REACT!

It is nigh impossible to write well structured, readable, well modularized code with it and not twist your mind in recursion from "lift state up" and "rendercycle downwards only"

Try writing a modular modal as a modern function component with interchangeable children (passeable to the component as it should be) that uses portals and returns the result of the passed children components.

Closest I found to it is:
c o d e s a n d b o x.io/s/7w6mq72l2q
(and its a fucking nightmare logic wise and readability wise)

And also I still wouldn't know right of the bat how to get the result from the passed child components with all the oneway binding CLUSTERFUCK.

And even if you manage to there is no chance to do it async as it should be.
You HAVE to write a lot of "HTML" tags in the DOM that practically should not be anywhere but in async functions.

In Angular this is a breeze and works like a charm.
Its not even much gray matter to it...

I can´t comprehend how companies decide to write real big web apps with it.

They must be a MESS to maintain.

For a small "four components that show a counter and fetch user images" - OK.
But fo a big webapp with a big team etc. etc.?

Asking stuff about it on Stackoverflow I got edited unsolicited as fuck and downvoted as fuck in an instant.
Nobody explained anything or even cared to look at my Stackblitz.
Unsolicited edit, downvote, closevote and of they go - no help provided whatsoever.
Its completely fine if you don't have time to help strangers - but then at least do not stomp on beginners like that.
I immediately regretted asking a toxic community like this something that I genuinely seem to not understand. Wasn't SO about helping people?
I deleted my post there and won't be coming back and doing something productive there anytime soon.

Out of respect for my clients budget I'm now doing it the ugly react way and forget about my software architecture standards but as soon as I can I will advise switching to Angular.

If you made it here: WOW
Thank you for giving me a vent to let off some steam :)

This Vue project I took over uses document.getElementById(...).innerHTML = stuff in its async created method.

That's the rant.

My boss wants to be asynchronous with php. Then to render the backend async he wants to use beanstalk using python to be scalable.

I said : we can use node.js it's already asynchronous. And we don't care about the langage php python...

Boss : node.js isn't scalable, there is no security it's not good enough, it's not enough safe. I code with php since 15 years and it's better than node. To much problem in the node.js version 0.12.

OK BUT NOW WE HAVE NODEJS VERSION 6 LTS. WAKE UP. OMG I GIVE IT UP LET'S GO.

I'm so fed up of this shitty ultra-ortodox industry

I've worked on many different projects, been in many different teams. It's an ever changing industry, but, surprisingly, it's so orthodox. Dev industry nowadays have some rules, that everybody adopts them as "best practices". You have to work on pull requests, and several of your teammates have to review your shit (as if they have nothing better to do).
I'm sick of people using fucking DTOs in shitty frameworks like Laravel. Using DTOs in Laravel is like putting mustard in a fucking chocolate cake.
I'm so fed up of SPAs and node.js. I've yet so see a single SPA that handles jwt tokens correctly. I'm tired of spending hours and hours, days and days, struggling with thousandls of layers of abstractions instead of being productive and getting the shit done.
Because end customers don't give a shit about your "best practices": They have a problem and you are getting paid for it to be solved, not for spending hours and hours struggling with stupid Javascript and its crazy async nature and their crappy libraries.

Damnit. I say. Now. I now feel better. Thanks for listening :)

Went to a "Javascript Cafe" wearing async t-shirt..

They put me last on the events queue :(

- Knock Knock
- Knock Knock

- Who's there?

- Your mysql query callback
- Your mysql query callback

Web Development is so easy!

I present to you: The Anonymous Asynchronous Self-Invoking Arrow Function.

(async () => {})();

You know you have chosen the wrong JS library when you read a function definition like this:

validateSync(schema, options, callback)

!rant

Goodbye Java I will not miss you at all! I swear ...

I do like it when making web services (especially that I can use Java8) but for Android you have been a torture. Hello sweet Kotlin! I shall embrace you and treat you like my newly born baby!!

Story is:
Working on a new project where I need to talk to a web service (also made by me).
Started writing in Java, all is cool and unit tests pass.
Downloaded Android Studio 3 Beta 1 and converted my Java code to Kotlin, That AsyncTask did not look nice in kotlin, converted it to async & await feature and I must admit lots of code removed, no more need to create a new fucking AsyncTask every time the app sneezes for data!

I feel like I'm working with C# but with difference in syntax.
My life is now complete :)

Just before the holidays started I was given a task by my manager, $M.

$M: "Kyntak, while I'm away I want you to look into this new way of starting $important_service"

$me: "Okay $M, is there a bug for this that explains what is needed?"

$M: "Yes, you should be able to find it"

Goes looking, finds someone else working on something connected but not the same, finds the code change that makes this available... It doesn't explain how to use it, when the async events fire or (well, to a junior engineer like me) really anything.

Message the other (very experienced) eng.
$me: "Hey I've been asked to make $important_service use the new starting API, can you tell me about?"

$eng: "Yup, here's a bug for that and I'm happy to answer any questions you have" *goes offline*

I read the bug. It doesn't mention the original problem I was trying to solve, it doesn't even mention $important_service. There's no design doc mentioned. The bug has a higher priority assigned than any of my other work. It has an expected completion date only days after I get back from holidays (which $M told me to take).

I try to contact $M and $eng. They've already left for holidays.

"Hmm"

Implements as much of the fairly inevitable boilerplate that I can infer from the bugs and surrounding code.

"Hmm"

So, I'm into my second week of holiday and am starting to think about the potential shit storm I may return to.

I hope the bug's priority was wrong.

A cannon was fired before it was even loaded.

#js

Im now working as a fulltime dev for 3 years. I do programming since im 9 and now that I collected some experience, I have to to say, its horrible. Seriously. What the fuck is wrong with german internship companys? Letting me do 3 years of FUCKING CRYSTAL REPORTS. IN A DEVELOPMENT TEAM THAT CONSISTS OF A TEAM LEAD THAT ACTUALLY HAS TO LEARN SHIT LIKE PROPER OOP AND ASYNC/AWAIT FROM ME. THEY EVEN ASKED ME IF I CAN DROP OF MY HOBBY PROJECTS TO WORK ON SAMPLES THAT THEY CAN LEARN FROM! NO! FUCK! JUST BECAUSE THESE DOUCHBAGS ARE TOO LAZY TO FUCKING LEARN TECHNOLOGY THEY SHOULD BE PASSIONATE ABOUT IN THEIR FREE TIME, IM NOT MAKING IT MY JOB TO FREAKING SHOW THEM THAT HAVING A STATIC CLASS CONTAINING ALL MODELS EVER EXISTED IN THE APP IS A BAD THING! SERIOUSLY, THERES ONLY ONE INSTANCE OF EVERY MODEL WE HAVE! AND THEN THEY BLAME SQL SERVER FOR RACE CONDITIONS WHEN TRYING ASYNC!!!! WHAT THE FUCK!! AND STILL, IF I TELL THEM WHATS WRONG, IM AN IDIOT BECAUSE IM A JUNIOR! Please tell me that i didnt waste 10 years of my life dedicating to such bullshit. Will that change? Is it company specific?

Dev sent out a code review request.
I take about an hour, ask questions, make suggestions, general feedback, etc.

Today I noticed none of my questions were answered, developer closed the review, and the code merged into the production branch.

So I email him, asking him why the review was closed and why none of my concerns were addressed before merging to production.

Dev: "No one responded or left feedback, so I thought it was OK to merge up."
Me: "I reviewed and left feedback within the hour you sent the request."
Dev: "Oh yea...you did. Sorry. The code is already in production, but if you still want to leave feedback, create a work item, and I'll take a look."

No you won't.

An example of the code...The dev added an async method to a test harness *console app*. Why? .. check in comment was "Improves performance and enhances the developer experience.."
NO IT DOESN'T!

OK..that's off my chest. No one is getting punched in the face today.

Dear other developers,

Don't throw exceptions in async callbacks goddammit. It doesn't abort the outer function where you think it does, and it crashes the app because you can't catch it.

I was just chatting with my dad. He used to be mostly a C# dev but changed jobs and is now doing mostly Java. He says he likes it better.... Because it doesn't have lambdas/anonymous functions.

Uh.... Java was the first and only language where you can define interface implementations in-line (aka a whole bunch of functions)...

And 1.8 supports lambdas for Interfaces that have a single function...

I bet he'll hate JS... Where functions are can be passed around like objects, ES6 now supports lambdas and await, async... and anonymous functions (apparently they're called arrow functions?)

TL;DR C# has changed quite a bit since the last time I used it.

So I'm working on a personal project, it's written in C#. When I needed to run a task on a separate thread. It has been years since the last time I worked with C#, so I googled it.

Me: "Async? Await? Task? This looks pretty fucking useful. When was this added?"

*Googles a bit*
Return .NET 4.5 in 2012. Current version 4.7.1.

Me: "What?! Last time I checked they were still in .NET 4. Shit!"

I've got a bit of catching up to do.

This new guy has a senior position and is 20 years older than me.
Im not a senior because I didn’t study (still have 10y of experience) and i don’t care about the title as Long as the salary is good.
But.. he sucks, he doesn’t know basics, keeps overengineering, I have to explain basic stuff to him over and over again like JOIN in sql, lambda, method references and async threads in java..

He probably makes much more than me and has a higher title..
I feel like nobody notices because I keep helping him to finish his shit.

That sucks!

Who ever come to idea to put JavaScript as backend language is insane.

I am coming from Java and now I am doing some work on Node project and I am loosing my mind.

Everything is an object but you have no idea what are his properties. There are call back, async, sync and mix. I don't even want to try debugging. There is no classes only object and a lot of functions everywhere.

The whole story with Node versions and playing with NVM. Don't even let me talk about Node modules.

Frustration and long development.

async / await is the best thing about javascript in my opinion

😍

@Android Question

Does all android devs use Async Task for their Json calls or you prefer to do them on Main Thread ?

Am just asking to improve my skills and get some senior programmers opinion

Not quite a rant, but looking for opinion/advice.

I have been programming for a little over a year now, excluding those cringy Lua scripting days with if statement hell. I'm pretty far ahead most of the people in my course (1st year Software Engineering), but I'm at this awkward point where I know quite a bit but not enough. All of my projects so far have been small 1-2 source file programs, mostly in javascript although Python is my main hoe. At the moment I'm reading a book on machine learning and I feel like I'm doing fine, not struggling too much with it, but I don't feel confident at all in my abilities. I had two programming internship interviews half a year ago, both of which I wasn't accepted in. I've been thinking of contributing to an open source project lately to get some "real world" experience but I can't find a good project to start with and just don't feel like I'm good enough. There are also a lot of small things I come across such as async and coroutines in Python which I'm not familiar with yet and they make my confidence drop even lower. I'm guessing most of you have been in a similar position. Would you have any advice for me? Should I search for a project or should I keep on studying with books?

Staring at code all weekend only to find on Monday an async method not being awaited

I need to delay execution of code in a for loop, how do I do that?

PHP: Sleep(3000)

Javascript:
const waitFor = (ms) => new Promise(r => setTimeout(r, ms))
const asyncForEach = (array, callback) => {
for (let index = 0; index < array.length; index++) {
await callback(array[index], index, array)
}
}

const start = async () => {
await asyncForEach([1, 2, 3], async (num) => {
await waitFor(50)
console.log(num)
})
console.log('Done')
}

start()

Fuck you Javascript

refactored model code to be async and use promises. executed successfully on first try.
ME: this looks suspicious, leta debug it!!!!

Sorry, need to vent.

In my current project I'm using two main libraries [slack client and k8s client], both official. And they both suck!

Okay, okay, their code doesn't really suck [apart from k8s severely violating Liskov's principle!]. The sucky part is not really their fault. It's the commonly used 3rd-party library that's fucked up.

Okhttp3

yeah yeah, here come all the booos. Let them all out.

1. In websockets it hard-caps frame size to 16mb w/o an ability to change it. So.. Forget about unchunked file transfers there... What's even worse - they close the websocket if the frame size exceeds that limit. Yep, instead of failing to send it kills the conn.

2. In websockets they are writing data completely async. Without any control handles.. No clue when the write starts, completes or fails. No callbacks, no promises, no nothing other feedback
3. In http requests they are splitting my request into multiple buffers. This fucks up the slack cluent, as I cannot post messages over 4050 chars in size . Thanks to the okhttp these long texts get split into multiple messages. Which effectively fucks up formatting [bold, italic, codeblocks, links,...], as the formatted blocks get torn apart. [didn't investigate this deeper: it's friday evening and it's kotlin, not java, so I saved myself from the trouble of parsing yet unknown syntax]

yes, okhttp is probably a good library for the most of it. Yes, people like it, but hell, these corner cases and weird design decisions drive me mad!

And it's not like I could swap it with anynother lib.. I don't depend on it -- other libs I need do!

Ted, Akka is a damn Scala library. Yeah yeah, I know you can fit it into your Java project if you really want to, but damn, you just end up with ugly Java syntax that tries and fails to be Scala. Just bloody well use Scala. Or use something more Java-esque like reactor if you *really* want to do async stuff and stay in Java land. But please, please don't use Akka in Java. The thing is a mess. I know it's asynchronous which in fairness does help in this application, but seriously just....

Wait... hang on... WHAT?! You're using the whole thing in an asynchronous reactive chain then just calling join() on everything?! What do you mean it's "mostly asynchronous but just blocks at the end?!?!" Do you like watching people suffer for no purpose, Ted? Do you?

Explaining Async at work...

"Why wait when you can ASYNC ":D

Heard this somewhere long back. Coming back to me now while learning node.

Ecma International, the organization in charge of managing the ECMAScript standard, has published the most recent version of the JavaScript language. ECMAScript 2016 (ES7 or JavaScript 7th Edition in the old naming scheme) comes with very few new features. The most important is that JavaScript developers will finally get a "raise to the power" operator, which was mysteriously left out of the standard for 20 years. The operator is **... It will also become much easier to search for data in a JavaScript array with Array.prototype.includes(), but support for async functions (initially announced for ES2016), has been deferred until next year's release. "From now on, expect smaller changelogs from the ECMAScript team," reports Softpedia, "since this was the plan set out last year. Fewer breaking changes means more time to migrate code, instead of having to rewrite entire applications, as developers did when the mammoth ES6 release came out last year."

Fuck NodeJS. I don't want you to be asynchronous sometimes. My gahwd I need like 3 deep nested loops just to get you to make a request and compile a damn JSON of requests.

I'm learning Golang goodbye forever node.

I just want to throw out there for Javascript developers, async and await are the two best things to ever happen to promises.

If I could I just wouldn't support email in any way shape anymore.

It's just too much hassle with all the spam filters and people just don't understand how email works.

Nobody fucking reads it anyway.... but everyone wants like a bazillion variations on stupid emails that go out that nobody will read.

They don't get that email is often instant ... but is actually async.

They don't understand that just because they got an email sent to their own distribution list ... and someone took them off the list... that doesn't mean that WE an outside group emailing that list stopped sending them messages.

Nobody actually looks at their spam filters until I tell them to do it for the 3rd time. And as if by magic folks at the same company don't 'have spam filter problems all the time'.

I had a company 'security' filter that straight up followed all the links in an email (that's fine ... we're good, I get that).... and then their stupid bot or whatever would actually click options on a form and fucking submit the fucking form!!!!!

I mean I get that maybe some sites have folks submit some shit and then deliver malware but that's gonna have consequences submitting shit none the less because I don't know it's just your fucking bot...

So they'd get various offers from our customers and bitch when they went to find it was already gone.

I’ve got to build an app in 3 weeks that handles basic image editing and async requests. It’s gotta support both iOS and Android.

It’s also gotta scan barcodes.

What should I use?

Cordova?
Cordova+ionic?
Titanium?
Xamarin?
Dart/flutter?
Try and cram it through in native java/Kotlin and swift?
Something I’m missing?

Avoid async void!

Today has been a battle of async methods and foreach loops

People around me and clients are increasingly saying i am a genius, because i show them an app i made in react-native or some crappy site i set up in a week as POC.

While im quite noobish still, i barely read publications out of interests, and most of the time i just put in async/await somewhere just to see if it makes the promise work or not, because i dont understand promises fully, and I think in general i just accomplished very little in the 5 years I have been programming

It is really putting pressure on my impostor syndrome, even more when i talk with my peers who can tell who was the driving force behind ES6 :/

So according to my manager its not really acceptable for me to sit at my desk and vent about what a colossal idiot my Tech Lead is. Fair enough i suppose. even though he feels the need to chime in on every technical decision when he himself doesnt understand how async code works. he thinks you can set a variable inside a promise and then return that variable outside the promise, because its after the call. This guy is a senior software engineer on an iOS team and I, a trainee, have more iOS experience than him.

When you've got a Node daemon with so much weird async shit going on you practically need a flux capacitor to sort out if all those promises get resolved in the order you need them to resolve.

Node: The most passive aggressive language I've had the displeasure of programming in.

Reference an undefined variable in a module? Prepare to waste your time hunting for it, because the runtime won't tell you about it until you reference a property or method on the quietly undefined module object.

Think you know how promises work? As a hiring manager, I've found that less than 5% of otherwise well-experienced devs are out of the Dunning Kruger danger zone.

Async causes edge cases and extra dev effort that add to the effort required to make a quality product.

Got a bug in one of your modules? Prepare yourself for some downtime because a single misplaced parentheses can take out the entire Node process, killing unrelated pages and even static file hosting.

All this makes for a programming experience that demands much higher cognitive load, creates more categories of bugs, and leads to code bloat/smell much more quickly than other commonly substituted languages.

From a business perspective, the money you save on scaling (assuming your app is more compute efficient under Node) is wasted on salaries and opportunity costs stemming from longer dev time, more QA, and more frequent outages.

IMO, Node is an awesome experiment, a fun language, a great tool for specific use cases, and a terrible fucking choice for an entire website.

Sometimes I look at my old code and I wish I could go back in time and punch my self in the face for writing that shit

But then I look at it as I'm actually improving so guess it's ok?

Spent 4 hours fixing callback mess I had in my ReactJs project, making it all as Promise and async hope I don't fuck up this time

After writing ~200 lines of code and then unit testing it

THE TESTS ALL PASS!!!

then I run them again just to be sure and they all pass but mocha is saying I am getting 40ms lag on some of my tests...

Noooo!!!

This is meant to be an async message passing system; I cannot have an input lag of 40ms :(

I really got in love with nodejs and shit. And to be honest, the whole async thing isn't that shitty either. I mean the performance itself seems to be whack af (see onoff benchmarks for reference) but your whole project is more responsive.

BUT FOR FUCKS SAKE THE ASYNC WRITE DOWN OF A SETTINGS FILE FOLLOWED BY SOME STUPID CRASH INDUCING MISTAKE I MADE MYSELF, LEADING TO THE WRITE FUCK UP AND ESSENTIALLY ERASE THE FUCKING CONTENTS OF THE DAMN SETTINGS FILE IS JUST LIKE SMEARING TOOTHPASTE ALL OVER MY FRIGGIN BALLSACK!

Overheard PHP developer say: "I don't like Node.js, it should be more like PHP where everything is async."

Honestly C# async/ await model is not that bad.

Not my hack but one I've seen hundreds of times:

Thread.sleep() because you don't know how to handle async calls

JavaScript is new the PHP.

Reading a stackoverflow question about async functions and await-usage, and lot of well-intended answers show no understanding of the concept. Some fail to understand that the scope is about promises. They don't know that, yes, *every* async function *always* returns a Promise and that within an async function it's synctically the same to do either `return x` or `Promise.resolve(x)` or `return new Promise((resolve) => {resolve(x)}), and they fail to realize what await does or doesn't do and are oblivious about how awaiting at certain stages can have huge performance impact when compared to either Promise.all or Bluebird.map.

Grasping promises is hard in the beginning, I get that. But please don't share your lack of understanding as fact.

I don't want to ever hear that you're proficient in JavaScript if you put a callback function call inside of an async function right after using the await command.

All you manage to do in the end was make a simple function that gets data to populate a dropdown menu into something that is absolutely more awful to look at than the worst callback hell possible.

Refactoring this code base has really questioned my sanity and how much I'm willing to spend on alcohol.

Generator functions should be treated like sorting algorithms: Not worth your time if all you have is 4 or less async instructions.
Callback hell is actually kind of nice and warm when you're a just a few levels down. If you're really confused by your obfuscated code, you suck at node.

What the hell happened to the dotnet ecosystem in terms of stacktraces and async.

You used to be able to pin down your issues to the freaking exact line number using a stacktrace, but now im building a azure function and this is the crap im served when it blows up: How do you debug this?

Just coded my first flutter app! The feeling when no async wait error appeared anymore was amazing. It uses the geolocation library to geht your current Position via GPS

Unrelated to programming:

If I'm doing async karaoke (i.e., I'm using an app like Smule where one person records one part and you join or vice versa) and the other person decides to randomly COME INTO MY LANE and not just sing my part, but sing it off-key, I get irrationally annoyed about it. It's great if they do that at the beginning of the song because then you can just bail. But when they do it at like the very end, I'm like ... 😬

Just got started with nodejs and I never thought I’d have to use async/await this early. Concurrency seemed like a far fetched thing. Feeling like a boss😎

Yo dawg, I heard you like asynchronous JavaScript, so I put a promise in your promise so you can promise while you promise

Actually in love with Promises, will convince my coworkers to use them as well tomorrow 🔥

boss. "I have a one o'clock meeting" Project Manager "uuuuuh, it's after one" boss: "it's an asynchronous meeting"

AND THERE WE GOT THE SYNC REQUEST ON THE FRONTEND LET'S FUCKING GO

Fuck ES/TS 😐

Been trying for hours now to get ionic 2 to work with either generators or async functions. Doesn't work because async for ES 5 is only supported with TS 2.1 which breaks the angular compiler. Also can't use generators (not supported for es5 at all by TS).

Also can't really change the ionic build process to just take es6 output instead of es5 and transpile because it's a convoluted mess in a separate node module instead of just a gulp file like with ionic 1.x.

Why is the JS ecosystem such a fucking mess?

```
public someMethod(index: string): Promise<void> {
return Promise.resolve(someAsyncFunction().then(() => {
return;
})
.catch((error) => {
this.logger.error(error);
throw error;
});
```

Somebdoy doesn't know their async / await syntax but they wanted aboard the promise-hype train. There is an entire class in that style.

How did I end up looking how to write asynchronous function in shell script whereas my task is to write a distributed chat app in Node.JS ?

Damn this is going to be complicated.

for my job I need to know,

Programming, C#, Optimization, Multithreading and Async code, Working certain tools, Reading difficult written code, Understanding, Physics, Networking, Rendering, Codeloops, Memory management, Profiling tools, Being able to make Jira tickets and read Jira tickets. Understanding source control branching, merging, push and pull. bug fixing.

And I write almost 1 line of code a week on average..

I'm a programmer.

Frontend using async calls same way as sync to load json config which contains backend api url. To make calls to backend API and sometimes file is not loaded before they call Api. This results to calling on current domain instead on domain from json file. Moreover, blaming that be is returning incorrect response.

I just want to combine python3 pygame with asyncio without asking Shiva for a dance.

I love developing JavaScript for Node.js applications until i have to create sequence diagrams with a lot of async calls :/

mocking my friend who can't async

I work with server side React rendering and I wanted to do an async job.

I tried to do it since more than 3 hours.

😕🔫

...

...

...

FUCK YOU REACT! GO IN HELL YOU FUCKING SYNCHRONYOUSHIT. FUCK IT!

😡😤

The problem: callback hell. Code would be indented by three hundred fucking spaces just to do some async work. Your code would end with thirty lines of closing curly brackets

Solution: async and await.

The problem, reborn: NoSQL. Code is indented by three hundred fucking spaces just to run a query. Your query ends with thirty lines of closing curly brackets.

tried to implement a tictactoe multiplayer server in node.js

protocoll should be HTTP vor easier WebClient implementation

switched to python, because i'm too dummp for async callback handling in node

I can remember a day which I really close to crying why my code doesn't work! Then I remember that fucking line of code should be run async! :/

There is no problem in life everything is in sync (Not async) ;)

I'm looking for a game recommendation to play with my (non-gamer) dad
What I'm looking for:
- Android
- Online 1vs1
- Turn based (async)
- Simple
- Free
- Lightweight if possible (my dad's phone is kind of old).
Something like checkers or chess but not checkers or chess :)

Wouldn't be node js a good fit for a performant message queue, I mean it's async from the bottom up, a low memory footprint and good rx support? Or what specific does a good mq require?

I just love optimizing stuff and here is my story I think somehow is very cool as you can see the progress just looking at two values.

//NOTE: This api relies on another api which is slow af. The requests are done here directly but later will be carried out async and in the background by using some ticket system.

1) First PoC
2) Used caching of requests and improved method to filter out unnecessary stuff
3) Optimized response formatting

NOTE to myself: Things are going too good...

Manager: We need to make the new system multi-threaded.
Previous Dev: Yes, so let's use Tasks everywhere! And by everywhere, I mean EVERYWHERE!!!

This is what I've found by delving into the code base which I have inherited!

Til that Node 10 has `for await ... in`. Basically looping async iterators. This changes everything!

Only in React packages...

When you follow the documentation to the exact dot and you get an error and nothing works.

And the stack trace gives you an error coming out of some deep async call, made many calls before the error.

Therefore the stack trace has nothing to tell you.

Equivalent of a brick falling on your head, just bad luck, who said programming should be deterministic anyway...

When I say "error in an async function" you say "no stack trace"!

"Error in an async function"!
"No stack trace"!
"No stack trace"!
"Error in an async function"!
"Unhandled promise rejection DEPRECATION WARNING Unhandled promise rejections will be shoved up your ass in node v7.coffee.9.10.666."

Finally got powerline working in tmux on my iMac. I found some obscure issue where there's an async problem occasionally on mac where you have to reload the daemon and config manually for it to work. Two days of fighting with this but it finally worked! It's a Christmas miracle!

Small rant because I’m new here, but…I hate async functions in JavaScript.
Especially when dealing with an API.

I love C# but I think that the addition of async/await did more harm than good. Hardly anyone can understand how to use it correctly and the only people who grok its black magic fuckery enough to write about it are MS employees. Try to do anything with it? Nope, there's a high falutin blog post by the likes of Stephen Cleary explaining why everything you know is wrong and you should have never even used async/await in the first place. Even worse is that to use the supposedly game-changing feature requires you to rewrite your entire fucking codebase.

Can you tell that I'm frustrated trying to wrap my head around async/await?

ok so i though of clearing my basics regarding concurrency and async behavior in programming. my end goal was to somehow reach rxjava and kotlin coroutines since these are the 2 common frameworks used in professional android dev . AND DAMN! since last 2 days am exploring apis and how stuff works and i have million milesss to cover.
I mean , here is a list of all the ways by which java8 (current version is java 15) achieves concurrency :BlockingQueue,ArrayBlockingQueue,DelayQueue,LinkedBlockingQueue,PriorityBlockingQueue,SynchronousQueue,BlockingDeque,LinkedBlockingDeque,ConcurrentMap,ConcurrentNavigableMap,CountDownLatch, CyclicBarrier,Exchanger,Semaphore,ExecutorService,Callable,Future,ThreadPoolExecutor,ScheduledExecutorService,ForkJoinPool, Lock,ReadWriteLock,AtomicInteger,AtomicLong,AtomicReference,AtomicStampedReference,AtomicIntegerArray,AtomicLongArray,AtomicReferenceArray

I have always just used threads and executors. maybe once or twice a handler/ looper and never a thread pool. these all stuff are so fucking much!

Any good async (if possible, also pipeline based) Networking libraries for C++ on Linux? I want to create a small Server which should be able to handle a big amount of TCP connections (~500) at the same time, using threadpools maybe, something like Netty for Java would be the best.

I expect somebody else has chosen this as well, but anyway:

Async.<any-function>, cause they brought me out of callback hell and taught me the undefined ways async...arghhhh fuck

- ok so I said I had to touch little bit of nodejs. It's a messenger like chatroom. Users data and the rest are stored in mysql. Chat messages are stored in mongodb. Found a funny issue. (Funny as in annoying that you just bang your head with your head while laughing funny) one mysql query in the node app is giving different order by result when you run it. I thought it was async issue. Turn out it's not. Said query works fine when running on phpmyadmin and the likes.

- I watched end game yesterday. And I'm sad. It's an end of an era. But also hopeful for various possibilities Marvel can do for future films.

- have you ever had such a great sex that afterwards she got serious headache and had to vomit?

Welcome to React where everything eventually becomes a race exception.

where async got rid of spaghetti callbacks , React introduced setState callback hell.

Explain js promises, async/await like i am 5.

Async tests are seriously fucking fragile there has to be something I'm missing here this is way too unreliable

It was a shit idea to try and get async to work in my first ever real programm meant to be used in production.
Unit tests are a bitch to make.
And now everything just kinda falls down on its own.

At least i learned a ton and got a lot of firsts out of the way.

HOLY FUCK I never thought that using async websockets in Django 3.x will be THAT much pain in the ass...
Also my next contribution will be their docs for sure, the examples are so fucking bad (linters are crying and begging me to kill them)

I have been trying to understand kotlin coroutines for a day and I UNDERSTOOD NOTHING!! 😭😭😭 makes me doubt my whole knowledge of concurrency and async programming and that's also probably too much incomplete.
Somebody please help!

if then you you can know read this this is
an async stdout

There is a Facebook group I’m a part of called “ReactJS Expert Community” and I can tell you it’s filled with anything but experts. Someone just posted on it asking what the difference between Axios and async/ await is. The only reason I’m part of this group is so I can feel good about myself when I screw up while coding xP

Spent 4 hours working with a buddy before realizing our failing code stemmed back to using sqlite3 Npm package, which is asynchronous. Switched to better-sqlite3, a synchronous sqlite package, and alls good.

What's the purpose of an async DB anyway? Seemed like it made storing and retrieving data a huge hassle.

So today I got to see one of the most stupid architectural choices I have ever seen.

They have a service-oriented architecture. Mainly Python and Elixir.
A lot of computation goes in the Python services.

And the Elixir services as used to expose RestApi. Basic ones, basically DB proxies.

Not a lot of async, or communication... Just plain CRUD.

Why the fuck do you use Elixir for that?? And now they can't recruit someone... And the CTO doesn't get why it was a stupid choice!!!

And in python, they use async functions with sync DB APIs...

Today on fucked up Javascript stuff: Call stacks whose bottom isn't an entry point or event handler

Pygame can handle kinect, but can't interface with asyncio. It freezes if I try to run event.wait in an executor. You may write the best game engine for a language, if you won't use language standards and don't support async, then it's shit.

The company has been moving projects away from ASP .NET to MVC .NET. One of the cited reasons was improved performance. The ASP .NET projects were not the fastest applications available, but were manageable.

The new MVC .NET projects are slower than snails. Every single page element is trying to do an async call to populate metadata elements. There are sometimes 50 or more controls per page due to the industry this software is used in. FML.

Yesterday a colleague of mine made a post on our company's workplace about receiving for the 3rd time the mvp award for .net. Today she wasn't able to explain Async await behavior to a junior dev. Nothing against it, just saying.

Going over some NodeJS code, and I feel like the scene from "Dude Where's My Car" - "And then....And then..."

Coming from almost three years of 99% python, this hurts my eyes so much

I'm still on a regular basis reminded of how I might be wrong despite the absolute certainty in how obviously wrong the other person is.

Lately I've been working on setting up this API with a fairly intricate database integration. One request can lead to multiple db calls if we're not careful, so we have been polishing up the implementation to guard against ddosing ourselves and dealing with thread-unsafe concurrency.

Someone on the team could happily report that they got rid of all async use so there should no longer be threading issues. "You mean it all runs sync now?" "I guess. It works at least".

I'm just internally pulling a surrender cobra. If this was pre-dev me I would have let him and everyone know what a stupidpants he is and that I thought he had some experience in api development. But let's not make an exception to the rule; I might be wrong. I mean I'm not, but let's pretend I could be. Let's pull down the changes and maybe set up a minimal example to demonstrate how this is a bad idea.

Funny story. He got rid of explicit calls to the database entirely. When resolving data, the query is instead constructed virtually and execution is deferred until the last step. Our functions are sync now because they don't call the database, and threading isn't an issue since there's only one call per request context.

Thank god I've learned to keep my mouth shut until I can prove with absolute conclusive certainty that they are wrong. Here's to another day of not making an ass of myself.

so ,i am getting confused in here regarding coroutines( the kotlin one)

synchronous calling :
"lets call api.fetchData() and wait until it returns data, then only we are gonna run the next line".

callback/async calling : "here's a bunch of lines that needs to be called after api.fetchData(). lets create a thread and move along, while passing the bunch of lines and api.fetchData() call. It doesn't matter weather the parent is alive or not, thread is gonna execute and then run those bunch of lines.

coroutines : " we know that api.fetchData() is gonna take 2-3 secs. so lets fire a coroutine for this api fetch and wait for 3 seconds before moving along. if the api takes <3 seconds, we will get the result before our next lines are executed. else we are going to ignore the result and execute out next codelines anyway "

is it right ? feels like coroutines is same as synchronous with wild estimations, for 1 call and slightly better in case of multiple calls
(like if i have to make 3 calls for fetchData(), in synchronous they would occur sequentially, but in coroutines, they will be executed parallely. but sometimes we require sequential execution so again coroutine is not the best thing there, right? )

Started learning python async with curio and trio just two days ago, and I must say I'm really having a blast.
I have a few pending ideas to combine it with websockets (also first time I'm learning how to use them).
Haven't had this much fun with python in a while!

Also, sidequestion: how can return a value from an async function with curio or trio? I can't find a proper answer or example about that, other than some hints about memory channels in trio

I am building a Django app where a function needs to be called asynchronously. I need to handle any interruptions like loss of internet connectivity during that time. How do I achieve this? Can anyone help?

Just had a cross training where the presenter kept pronouncing asynchronous and async as "awe-synchronous" and "awe-sync".

Nice job, but not awe-some.

Reading a book on React and how data/changes flow one way... down.

Oh hm... sounds different...

Then after an hour or more it goes oh yeah, you can pass children callbacks.

OH WTF!!!! That's like every single language (passing the parent itself as an Interfaces), Android Fragments, Node/Express, Async finding)

That's pretty much MVC?

How would you handle this:
You generate an id
You chech the db if it is not taken
If it is taken you generate a new one and check again.
You then save the new item with the generated id.

How do you ensure that between the time you checked and the time you added the item some other call did not try to also add an item with the same id.
Async mvc
C# and dotnet core with ef core

Most satisfying bug, it was something with good old $.ajax, way back when Axios wasn't a thing and SPAs weren't so widely used.

I was somehow able to fix the call params for a file that would not load with any other setup. Maybe it was just setting async to sync or something like that, however the thing is I was not familiar with AJAX at all, but I managed to get it run.

Then I googled, why its working and figured out all the answers on SO and other pages were the exact thing i set up for my call. I was so proud

some context: I was struggling with this bug for days and asked more experienced web devs, everybody answered, your code should just work fine.

Maybe thats why I have a positive relation with SO, because the first thing i searched there was something that I figured out myself, haha

After far too many hours dealing with unproperly behaving click listener and lost references, I just found out that the real problem was with poorly handled async DB access.

Frustrated but happy to find the problem source.

I believe everyone have the same from time to time. At least now I can share my feels with you.
But... time to move forward!

async void day()
{
wakeup();
CheckDevRant();
DoShit();
If(IsInMood)
GoOffice();
while(IsInMood)
{
Eat();
Game();
Code();
}
Eat();
Sleep()
await day();
}

Man I am having a bad day. Stack overflow

I have a strange satisfaction whenever my asynchronous js code filled with promises executes in the order that I write them even though it has no bearing in the correctness of the program.

EDIT: the async tasks are supposed to execute in identical times in theory

learn to use redux with async actions and find out that there redux-sagas and re-read more documentation.

Sooo. My team and I have module we're supposed to be porting to async code and aiohttp will not work. The server keeps rejecting the byte payload, but if we use synch code like the requests library, it works fine. The code is like identical, the only difference is async. It's been really frustrating because another drop in async version of requests (httpx) works just fine! I don't want to use httpx, the rest of our codebase is already using aiohttp! We think the problem is with gzip encoding being handled incorrectly by aiohttp. I've reported the issue.

Our lead dev has convinced the board to move the new software suite forward into .Net Core 3. Much of his reasoning is sound, a mainstay of which is the cost and ease of hiring developers to actually make and maintain it.

My own roadmap with the company focuses around one of these products, so I am to become the core developer and maintainer. Given thats the case, given that my primary skill is with Javascript/Node and given that we have deadlines, I am going to make the case today that this product might be better built in Node.

We are going for a microservices architecture. Combined with Typescript for type safety as the code base gets bigger, I am not sure I can think of many real advantages to choosing .NET instead. It will benefit from its async I/O later too, as the plan is to build in API driven dynamic UI down the road.

He is a fierce man, and I am the junior. Wish me luck.

Hey guys I've a problem I've been trying to solve for a while. Also I'm a college student so my knowledge isn't going to be the greatest so go easy on me if it's simple to solve😂. So I'm creating a real time licence plate detector using yolo lite, my own deep learning ocr and plan to add the model to fast api. So as an input to the rest api, the user will submit a IP camera link for openCV to get individual frames for preprocessing before yolo predictions. The problem I have is how to I handle multiple real time IP camera feeds at once?. Ive been researching multi threading but read that it can cause issues with async definitions in fast api. Any advice will be greatly appreciated and if more information is needed just shout!.

Useless JS library #0 ready.
Communication among windows in the same window group (iframes and popups with a common root), with dynamically generated objects, so it feels as though you were just calling local async methods.
Useless JS library #1 will be a layout manager, a program that manages panes and tabs, context menus, toolbars and a menubar much like Visual Studio, and let all of that communicate through Useless JS library #0.
Since JS is sloooooow, I try to make everything run the fastest possible, trading startup for runtime resource usage. #0 fulfills this, any message will take exactly 4 stops, although registering a callable method set takes .3 sec.

Solved django recruitment tests. Rejected because they seek someone who know django and I said I don’t know django cause I was using raw python, sql and writing async apps.
What I can say ? Thanks, lol

Who would win?

1) 800 futuristc async error fetching fs.writeFile

2) 800 fs.writeFileSync bois

Bloody fucking Android! Updates, updates and more updates! My development Nexus 5X won't allow me to sideload apps since it updated... Hello, printf debugging! Goodbye, profiler and debugger!

My hate for Android grows with each version after 4.0.$something... 2 was shit, I missed 3, 4 was OK, and since then it's going steeply down.

And don't get me started on Material Design...! Good luck figuring out what's a button and what's a label...

And what's up with the "let's keep all apps running all the time to save a few ms on start" philosophy!? Who thought that is a good idea!? Yeah, System.exit(0) works, but... Is it so hard to determine when it's not needed anymore (has no services running etc.)? Why should a web browser (for example) stay in memory after I quit? Minimize is a thing (Home button), why make it so confusing?

Another thing - feedback-less async tasks - why? I like to know when it is working in the background... How the hell am I supposed to find out if it is supposed to do this or if it is frozen?

And Android deciding to kill your process whenever it pleases without any callback... Happened to me once with an Activity in the foreground (no exceptions anywhere in my app, it just quit). How do you do IO properly? It seems you can't guarantee some file or socket or something that must be closed doesn't stay open (requiring to restart Bluetooth 'cause the socket wasn't closed, for example)...

Anyone out there a Scala fan? I am! Seems like most of the stories here are quite negative but positively is my thing so here's my 2 cents:

Scala is an amazing data processing language. It's a functional language with a lot of really great things like a consistent collection library api, case classes, brilliant async library's like Akka Actors, and plenty of solid learning resources like Twitter school and Martin Odersky's online course.

Got a massive deadline coming up and thought why not add to the pressure and install VsVim as well.
Have to say I was pleasantly surprised, with that and the navigate to feature you don’t need a mouse at all and I barely know vim. :q is so much easier on the hands than ctrl+f4 now if only I could work out a macro to automatically add async modifiers

Debugging code that mutates somewhere between returning a response and exiting trough nginx. Dafuq is this madness. It happens seemingly at random.
An async func calls the server that responds in some gibberish madness 1 in 100 times. How am i supposed to debug this! 🤬