<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>console on Curtis Timson</title><link>https://hugo.curtiscode.dev/tags/console/</link><description>Recent content in console on Curtis Timson</description><generator>Hugo -- gohugo.io</generator><language>en-GB</language><lastBuildDate>Thu, 28 Mar 2013 00:00:00 +0000</lastBuildDate><atom:link href="https://hugo.curtiscode.dev/tags/console/index.xml" rel="self" type="application/rss+xml"/><item><title>console.log() vs alert() when debugging</title><link>https://hugo.curtiscode.dev/post/js/console-log-vs-alert-when-debugging/</link><pubDate>Thu, 28 Mar 2013 00:00:00 +0000</pubDate><guid>https://hugo.curtiscode.dev/post/js/console-log-vs-alert-when-debugging/</guid><description>Using console.log() is a great way of getting quick results about what variables are holding what values at which point, and which areas of code are being called, without having to debug.
Before javascript debugging became so accessible, one of the only ways of checking the values of your variables would be to call alert(). However, this wasn’t ideal as it would stop the script from running while the alert() was displayed, preventing the script from continuing its usual process.</description></item></channel></rss>