My understanding was that each await would "block" (creates a new function in a then block that will get execed once the promise resolves).
if you wanted to run the two in parallel you would have to Promise.all([promise1, promise2]).then(fn)
There's no legal or culinary definition for any of these. You can call it sorbet, granita, water ice, or probably one of many other local names and it'll have similar ingredients, but maybe a different ratio or texture. You can't even get Italians to agree on what a granita should be.
I recently programmed an application for a test bench of electric motors, where I could basically translate the flow chart I was given by the engineers to a state machine. Out of the state machine I handled all concerns like UI, hardware controlling and persistence via events.
That's an empirical question, not theoretical, so it's "has been", not "can be". Interesting question. Like the Bust Beaver function, apparently unknown.
I would have liked to have seen some comparisons. Showing javascript syntax but then not showing anything else and then saying its good is not really an argument.
And aren't frontend dev essentially forced to use javascript since we can't compile to anything else at the current time? yes webasm is coming
and yes there are languages that compile to js
