I am not alone in being a web developer, and console.log() is the workhorse of debugging in the browser.

However in Qbs, console.log() seems to be silently ignored, instead you are supposed to use console.info(). This has lead me and presumably many other users to sessions of debugging where we get NO console output, and no errors or warning while being 100% certain of putting the necessary log statements in our code.

I hereby ask that one of following things happen:

1. console.log() creates an error that is visible in log output when you try to use it, with a statement similar to "oh so you think this is the web? Try console.info() like a real man you beta loser"
2. Using console.log() has the exact same effect as console.info() with an optional polite warning that console.info() should be used instead
3. console.info() is deprecated in it's entirety and everyone should use console.log() from now on

As long as I know that I did something wrong, I will be happy.