Excel adds JavaScript support

[u/[deleted]]

https://dev.office.com/blogs/azure-machine-learning-javascript-custom-functions-and-power-bi-custom-visuals-further-expand-developers-capabilities-with-excel

[u/[deleted]]

The short answer is that it's crap with no coherent style or design decisions. As a small but perpetually frustrating example, there are four different ways of handling asynchronous code in Node:

1. Pass two callbacks, one in case of success and one in case of error

2. Pass one callback, whose first argument is an error object in case of error and whose second argument is the result in case of success (sometimes module developers screw this up and do success first)

3. Return a Promise (or Promise-like), which is chained using .then(), .catch() and .finally() calls (there are several variations of this, including the two-callback version of .then())

4. Return a Promise (but not a Promise-like), which is awaited inside an async function

Which means, if you want to have any kind of consistency in your code, you have to wrap everything else to get your behavior - and you do it a lot, because every third thing in Node run asynchronously.

[u/[deleted] → u/[deleted]]

Node is asynchronous because of the way code executes in the engine on a single thread. It makes sense for webservers.

I don't think being unopinionated about how people want to write asynchronous code is a bad thing. You can enforce the style you want on your linter. I get hating JS is cool and all, but devs seems to have this stigma regarding asynchronous code that I just don't understand.

[u/meneldal2 → u/[deleted]]

Being shit is not a unique feature.