- https://developers.google.com/speed/libraries
- http://www.w3.org/TR/cors/#access-control-allow-origin-response-header
- http://www.w3.org/TR/resource-timing/#cross-origin-resources
- https://d3js.org/
- http://dojotoolkit.org/
- http://www.sencha.com/products/extcore
- http://hammerjs.github.io/
- https://github.com/material-motion/indefinite-observable-js
- http://jquery.com/
- http://jquerymobile.com/
- http://jqueryui.com/
- https://github.com/material-motion/material-motion-js
- http://mootools.net/
- https://github.com/googlei18n/myanmar-tools/
- http://prototypejs.org/
- http://script.aculo.us/
- https://github.com/google/shaka-player/
- http://youtube.github.io/spfjs/
- https://github.com/swfobject/swfobject
- http://threejs.org/
- https://github.com/typekit/webfontloader
- https://developer.chrome.com/devtools
- https://developer.mozilla.org/en-US/docs/Tools
- http://msdn.microsoft.com/library/ie/bg182326.aspx
- https://creativecommons.org/licenses/by/4.0/
- https://www.apache.org/licenses/LICENSE-2.0
- https://developers.google.com/site-policies
- http://groups.google.com/group/Google-AJAX-Search-API
- https://developers.google.com/
After the rust string overview of its internal substructures, let's see if c++ QString storage is more light, but first we'r going to take a look to the c++ standard string object: At first sight we can see the allocation and deallocation created by the clang++ compiler, and the DAT_00400d34 is the string. If we use same algorithm than the rust code but in c++: We have a different decompilation layout. Note that the Ghidra scans very fast the c++ binaries, and with rust binaries gets crazy for a while. Locating main is also very simple in a c++ compiled binary, indeed is more low-level than rust. The byte array is initialized with a simply move instruction: 00400c4b 48 b8 68 MOV RAX,0x6f77206f6c6c6568 And basic_string generates the string, in the case of rust this was carazy endless set of calls, detected by ghidra as a runtime, but nevertheless the basic_str...
Comments