@Danidre
I'm Danidre, a game programmer, web developer, and software engineer!
I'm Danidre, an author, game programmer, web developer, and software engineer!
Nothing here yet.
I have understood the generals of this for quite a while, but could not explain it. Now I better can! I wonder if this is why you cannot use a while loop to block the thread while waiting for an asynchronous task to be completed. The browser delegates that task to another thread, and when that promise is resolved, it will place the response/callback in the event queue. However, if a while loop is ongoing (like while (true) ) then it will keep iterating forever, placing its iterations into the call stack continuously. Thus, the call stack will never be empty for the promise in the event loop to reach the call stack and proceed with the code. Is my thought process correct here?
Nice article. Some feedback would be to review the formatting of code blocks, since the indentations and syntaxes are sometimes incorrect. For example, instead of: function webConfirm ( ) { var x; if (confirm( "Do you want to exit?" ) == true ) { x = "Welcome back!" ; } else { x = "Bye!" ; } document .getElementById( "exit" ).innerHTML = x; } It would be: function webConfirm ( ) { var x; if (confirm( "Do you want to exit?" ) == true ) { x = "Welcome back!" ; } else { x = "Bye!" ; } document .getElementById( "exit" ).innerHTML = x; } Similarly, instead of: If (message === true ) { It would be: if (message === true ) {
Congratulations on your first project, and hackathon entry! One feedback to give would be to try to get a short domain name as well. We can use simple short slugs for links, but https://urlshortner-gamma-six.vercel.app/ is a really long url to type or remember. P.S. Check out https://urlshortner-gamma-six.vercel.app/danidre, https://urlshortner-gamma-six.vercel.app/projectree, and https://urlshortner-gamma-six.vercel.app/root 😉
Eleftheria Batsou Your error was indeed strange, as I had battle tested and been unable to discover that bug during development. Thank you for the feedback, by the way! I appreciate those suggestions. Originally, I left both the "Save" and "Publish" buttons there, telling anonymous users to "Sign in to save" or "Sign in to publish", incentivizing them to register (call to action). However, as per your suggestions I can blur/disable the buttons until they have added projects and then save. Will put it on the list to work on when I've gotten the clear that I can continue working on it. 😁