Well that discussion is pretty crazy and very polarized.
JSMin guy thinks fixing it is stupid, and the bootstrap guy says that since it works in browsers it should work in JSMin.
So they've reached an impasse. Unfortunately emotions and strong words were used right away which polarizes the conversation.
Being completely pragmatic about it, it seems that bootstrap should probably change, instead of JSMin. But I don't think either will so both sides lose, and potentially make their tools available to a smaller audience.
Please send a pull request to Crockford :)
You know how when you were a kid, you used to argue with the answerbook? The answer book was right.
STFU
God says... spirit you're_nuts so_he_sess humility anger fight I_could_be_wrong so_let_it_be_done Kenya I_don't_care Ireland what_would_Jesus_do failure_is_not_an_option Oh_really you_don't_say bummer chill_out smurfs Shakespeare nut_job do_not_disturb African not_that_theres_anything_wrong couldn't_be_better how_about_a_comic woot so_he_sess how_about_that virtue are_you_deaf insane service_sector I'll_let_you_know strip ice_cream This_is_confusing chump_change United_Kingdom Ghost I_can't_believe_it maybe_I_didn't_make_it_clear honesty Yes_you_are that's_for_me_to_know endeavor failure_to_communicate what_part_of_God_do_you_not_understand Uruguay
Hey all,
Mr. Crockford has recently refused to fix JSMin (https://github.com/twitter/bootstrap/issues/3057).
Thus, I've fixed it. You can get the updated code from https://github.com/shawnpresser/JSMin/blob/master/jsmin.c
The fix was simple. It simply scans for "newline, optional whitespace, exclamation point" and replaces the newline with a semicolon.
I've given special attention to safety. This code works exactly as JSMin did, except it implements the aforementioned semicolon substitution, thus supporting the Javascript idiom:
I hope this proves useful to someone (possibly the authors of Bootstrap). It was a fun project.