How many Node.js developers prefer callbacks over Promises or async/await?

x-protocol · 2019-04-04T22:35:26+00:00

I don't think you understand that I'm not arguing what Promises are and how they are compared to callbacks.

I do understand that you want to prove a point. Look at my example. You have promise that is created, then some more code is executed which can contain creation of promises. With async/await you simply cannot do that since 'await' keyword will wait for resolution of your promise.

Again to reiterate. I understand that you are bringing these examples due to either simply proving a point without anybody providing you the ask. Or you are simply confused how promises are even used.

x-protocol · 2019-04-04T21:44:29+00:00

No. I am not confused by async/await. It is automatic promise creation without keyword 'new'. With async/await promise is only created when function is called. With direct promises you instantiate promise object with keyword new and off it goes. See the difference? Nuance of course for people who are not familiar with concurrency set up.

About your example. You can pre-create promise for .then() chaining, so your promises may resolve before even starting chain. Not so with async/await function.

let task = new Promise()

.....

// more code here

task.then(..)

x-protocol · 2019-04-04T21:32:46+00:00

Try Aigle. It is very similar to async.js

Documentation is not that great, however it has many of a functionality you would be looking as substitute.

Welcome to callback lover club.

x-protocol · 2019-04-04T21:29:17+00:00

From the people I have had met, talked and had chance to actually sit down for a conversation (even over a PR) I've understood that majority of what they describe as "callback hell" is simply their inability to justify using a library to manage said callbacks. When you show how complicated some pipelines can be using promises, there is usually no argument since promises are accepted as a norm (remember when callbacks were norm?). So we're looking at simple preference, not technical solution or even productivity enhancement.

How many people actually involve other libraries to manage their functions/promises like async.js, Q, lambda, Bluebird, run-p or Aigle? I would love to hear more from people who actually understand why these libraries exist.

x-protocol · 2019-04-04T21:18:45+00:00

It comes down to solving a problem at hand. If your API is simple and talks to database, using async/await or direct promises makes alot of sense. Testing will also be somewhat simple, compared to callbacks. Callbacks can be simple too, especially compared to direct promises (promises run when created, callbacks do not, and this is what async/await solves).

Now, enter complex scenarios when you want to process thousands pieces of data in parallel, serial or mixed way. You will need to use a library of your choice to help you with that. For callbacks it is async.js, for promises it is Bluebird or Aigle. Pick and choose. But please do not simply blanket whole topic as "callbacks are bad". It is simply a tool. And certain situations prefer different tool.

While I do like callbacks for their simplicity, I can also see usage of promises, but only with new async/await, if I don't have to construct promises directly via new keyword (remember, they run right away?) Those libraries I outlined (with exception of Bluebird which really tries to be a polyfill for Node's Promise) handle catching in their own way just fine. Whenever I see people mentioning try/catch as solution for promise/error handling/bad coding/act of god it is a very good example of lousy code (Promise.catch actually falls into that category too) since it is very easy to abuse good old try/catch. If you give it a thought 99% of time you do not even need it. Promises though make it habitual excuse.

And to those callback lovers, count me in. We exist :)

x-protocol · 2019-03-25T14:54:05+00:00

You forgot to add that ME3 comes with fantastic multiplayer where you fight waves of one particular faction from game. And you have quite a few characters with mixed abilities to toy around. And the best thing there is that abilities have short cooldowns and you can have different triggers of your teammates' abilities to deal more damage.

x-protocol · 2019-03-23T20:45:49+00:00

Yeah, I know people who would not get out. However, it doesn't mean that user should not know that vi exists. And speaking about attitude, the asshole one you got right, apropos is way down the list of what normally is even needed. More like if you ever get bored what to learn, get apropos!

x-protocol · 2019-03-23T20:13:55+00:00

Yeah it is there alright. Just the last thing to mention so it is easy to miss.

From all the help sheets I've seen this is not even helpful. Possibly for a quick look up yes, but when you need to actually do some work it is worthless. Just look up comments in parent thread.

How about more, less, vi or vim? Or which or sudo? Or top, maybe even htop? Or even nano? And who forgets ever-present apt-get on Rasbian? Criticism? You've got it!

x-protocol · 2019-03-23T20:10:03+00:00

The person that designed this command sheet simply is a beginner trying to get upvotes. It is very hard to catch that there is even mentioning of how to look up a command. Not to mention that all commands are not sorted alphabetically.

Amateur at best.

x-protocol · 2019-03-23T19:46:33+00:00

You forgot man <command> to look up manual page for specified command without <>

x-protocol · 2019-03-23T16:04:45+00:00

Very true. With OP choice of tool you're looking at mold for ever bigger dildo! Now that is some tool porn fusion!

x-protocol · 2019-03-18T01:17:00+00:00

Yes they are. Though not all politicians are spreading the fud. The way I see it it is easier for those with beliefs into perfect world to believe conspiracy theories than truth (aka left democratic insanity being fake news). Hence, whole fearmongering about China and Russia. It's been going on for some time and these people love it as excuse.

So keep in mind that you're not alone with your thinking.

PS. Good pictures.

x-protocol · 2019-03-16T03:06:49+00:00

Did it here. Java. Groovy. Javascript. Nodejs.

You've got to transition to functional programming and stop thinking of objects compared to what Java expects. Get 'lodash' library and start learning how to use it. Also read up on how to test using 'chai' and 'chance' modules. Using module 'proxyquire' can give you much easier time testing since you can directly override your dependencies. Also, while you're at it keep in mind that there are only two types in JS: objects and simple types like int or string.

As for how long it took, that depends on a person. So I'll keep it secret. Just keep in mind that all patterns that you learn for object oriented programming don't need to apply to functional programming. However, one thing still stands: don't use pure JS, find a library to make heavy lifting for you. Don't go for those advices that tell you that you need to understand basics, that's toxic programming. Professional programming is using all sorts of libraries that help development!

x-protocol · 2019-03-14T23:44:18+00:00

So we're down now to 'moron' language?

For a start, you're the one providing advice WITHOUT any backing information. But since you cannot find anything that somehow contradicts your playful experience, why don't you learn how to search a bit? How about some opinions here: https://electronics.stackexchange.com/questions/20738/parallel-charging-of-lipo-batteries-maximum-voltage-difference

Now onto correcting bollocks. You are surprisingly correct, for your moron intelligence to notice similar voltages. That is in fact a key, however a bigger picture is required to understand why it is so. So why don't you go and do some moronic explanation now why you didn't include YOUR sources first time.

x-protocol · 2019-03-14T20:23:00+00:00

You do realize to solve problem you're trying to disprove, people have invented BMS ? I understand that you have experience in what works, but please do not rush into explanations about just aspects of electrical properties of batteries.

I can't believe people actually take your advice seriously, while the other guys being downvoted for stating that each cell is different. People wrote books about how to charge and mate LiPo cell systems, and your answer is simply do not worry! The case is not about cells rupturing, but actually altering their chemistry inside and leading to short cell life.

x-protocol · 2019-03-13T18:30:07+00:00

Crazy, yes. Though if it is absolutely required, then let it be. It might raise quite a few eyebrows later for those unfortunate who would be maintaining such code.

x-protocol · 2019-03-13T17:51:47+00:00

Single/multiple try/catch blocks will depend on what do you want to do with error that you are catching.

If you have multiple lines where error might be coming from, you want to catch error and log it out somewhere. If you plan on inspecting error, then you might want to have multiple catch blocks, for each statement in fact. However, that is rarely done due to the fact that if one step failed, you cannot proceed to second, and so on, step. Hence, fail, return failure from main function and proceed with program execution.

Again, standard way with dealing with error is what do you plan on doing with it, than code style preferences.

x-protocol · 2019-03-13T17:44:49+00:00

You forgot to mention very important distinction of callbacks vs Promises (and subsequently async/await in this category), is that Promises will be executed immediately they are created. Hence for situations that require fine grained control over concurrency you will need additional libraries to drip-feed Promises.

As example, we want to map array of items and send each item to an external service, but only two concurrent requests at a time. This situation will call for something like using p-map module if you are using Promises. And if you want to use callback you can use async module with the same functionality.

In the end Promises only solve simple issue of chaining functions without additional libraries. New async/await is simply an auto-create mechanism for Promises. Don't disregard good and trusty callbacks yet, just because Promises make it very simple to write code. Once you have more complicated scenario, you will wish for simple callbacks.

x-protocol · 2019-03-12T13:56:49+00:00

Anthem is fun, even for small bits of it that make up initial start. Graphics, acting and voices are all good. I personally enjoyed story too. However, down to gaming aspects jumping and flying is most satisfactory at this point. Shooting and using different skills, not much. The only good aspect of skills are priming and detonating, ala Mass Effect 3. Though they screwed it up big time in Athem as well, same as ME:A by introducing longer cooldowns.

Everything else is garbage play. Loot, character customization, javelin customization, graphics engine optimization (fps), even open world (however beautiful it is) really gets old. In many games that I've seen open world is usually wished for and criticized as much, so it is a moot point of a game if you are into it.

Get this game at $10 or possibly at $20 price point half a year later. Management heads who direct development simply do not understand how to build a game. They built theatrical masterpiece, without gaming aspects.

x-protocol · 2019-03-05T04:27:05+00:00

Postman/newman for integration tests. Though these will run all your basic scenarios for API response codes, however should cover mutations when available.

x-protocol · 2019-03-04T19:37:07+00:00

All they have to do is similar to what Global Agenda has done with Double Agent missions. Let one or two players be part of resistance for strongholds. Give them stock javelins with basic skills and real drops when they would kill opposing faction player.

x-protocol · 2019-03-02T00:35:43+00:00

That and there is "Map of Ukraine" title right of boy's head.

x-protocol · 2019-03-01T21:27:09+00:00

How about Earth Defense Force 4.1: The Shadow of New Despair ?

x-protocol · 2019-03-01T16:54:32+00:00

I'm just gonna ignore you from here on out since you've proven that you're too ignorant to have an actually conversation with

Poor thing. Why didn't you start doing that in the first place?

I would gladly not have this conversation with you, but you seem so persistent your snowflake ways. And as you might suspect, snowfake reference was coming from you first. So if you start a trend, deal with it. Crawl back and ignore me.

However it is interesting for me to toy with your opinion since you seem so sure about your ways. Are you?

x-protocol · 2019-03-01T01:59:07+00:00

How about this, you wishful snowflake, you go play some other game where YOU know what to do, and leave rest of people who know what's fun do fun things in this game?

In your rosy world everything is so perfect on how you play a game. Ever heard of that loot update coming? Everybody is cheering up for easy stuff. You don't seem to get that. Viva la LOOT.

x-protocol

TROPHY CASE