HN Explorer

20 comments

[ 3.8 ms ] story [ 36.4 ms ] thread
xentronium
I don't like this new trend of giving libraries cute names and not giving a reader any idea about what your library does. I read the blog post and README file on github and still don't know what Chimney does.
mapleoin
It burns logs.
bazzargh
No, it removes console.log statements; really not at all obvious without reading the code. The metonymy of referring to console.log as the log when it's the thing that creates the log doesn't help at all.
nicholassmith
You throw logs on the fire, the fire burns. It's a toy, the more logs you give it, the more the ASCII fire burns.
[dead] eulo
If you're a javascript dev it's pretty obvious from the README that it removes console.log statements from .js files.
saurik
Like "bison", or "libiberty"? I fail to see how this is a "new trend". (edit:) Oh, you are also complaining about the readme being obtuse; yeah, I agree with that problem: documentation other than "a short readme in markdown" used to be much more valued. :(
nsxwolf
I actually find this submission downright offensive. I clicked in good faith and was presented with no content.
mrspeaker
I was thinking that you were over-reacting and just not getting the joke. But that's because I thought it was just a joke repo that console.logged things until your CPU spiked and warmed up your computer thereby "keeping you warm". Perhaps being a tiny bit less cute could help after all.
zacharyvoase
I don't get it. Is console.log a really annoying artefact that node.js creates or something?
Couto
console.log is a debug statement used in Javascript code. However is not supported in older browsers like IE8...

If you forget to remove then, IE8 will crash and burn...

It may also affect performance, although that is usually negligible...

4lun
Stripping out console.log as part of a build process tends to be the ideal solution, but on smaller projects it's nice to leave them intact so the below is my preferred method:

if (typeof console == "undefined") { console = { log: function() {} }; };

masklinn
> console.log is a debug statement used in Javascript code. However is not supported in older browsers like IE8...

That is not quite correct. IE8 (and IE9 I believe) support `console.log`, but only when the developer tools are open.

Needless to say, it is rather frustrating.

easytiger
isn't that also true of the other browsers?
tbassetto
It is true for Firefox 4 and older.
masklinn
Not that I know of. It was probably an issue in Firefox if Firebug wasn't installed before it got built-in devtools.
zacharyvoase
That was silly of me. I've used console.log countless times before. I just never thought of it as a thing that could be 'burned'.
kidh0
I guess that it should give a better view about what it really does. Maybe a screenshot?
Kudos
A screenshot would be nice. I presumed it silently removed console.logs from your code, only to wonder why the fuck so much code was needed for that ;)
bazzargh
It looks to me like this will not remove window.console.log statements - which developers would insert to bypass the fact that console.log is normally banned by jslint for production.