I just realized that #2013 by @juukie14 is identical with my pull request. (I honestly didn't see his either.) Pick whatever you prefer.

Nice to know I'm not the only one who would like to have a change for this ;)

The same change was suggested in the Laravel4 port; loic-sharma/profiler#24

But that gave me problems. And I think the profiler uses the noConflict option, for this reason, right?

@barryvdh The escaping is for older browser support. Remember the CDATA stuff and XHTML? Well, this is widely supported and won't mess with an older browser.

The noConflict option is so that the $ function is not aliased to jQuery; so far as I know it has no effect against jQuery loading itself into the jQuery object. So, it won't create a jQuery173 object but will write itself to jQuery and overwrite any previously loaded copies of the library. Just load an L3 project and play with the console. Eventually you will find something missing.

Well yeah, I just looked at html5 boilerplate, and they don't feel like it is neccesary, while they support atleast IE7; https://github.com/h5bp/html5-boilerplate/blob/master/index.html#L28

But I started having trouble when a similar patch was supplied to the L4 profiler..

What trouble happened? If you describe it, I can probably tell you why.

Well, I haven't really figured out what it was exactly, only that it started happening since that change, and when the change was reverted, it was fixed.
It stopped TinyMCE (3.x) from loading, and gave a console error (but can't exactly remember the error)

Well, without this code I'm experiencing trouble of my own. Custom selectors and plugin don't work from the console for debugging, and trying to troubleshoot code has become complicated thanks to 1.7.3 overwriting 1.9.1 and all the plugins that have already been loaded.

Since you haven't given me the console output, I have to say that it's a version conflict and nothing more. You're probably using a version of TinyMCE incompatible with one of the versions of jQuery.

Duplicate issue.