arstechnica.com— Since its release a few weeks ago, curious developers have been sniffing through the source code for Google's new Chrome web browser.
Sep 22, 2008View in Crawl 4
Bury TheRealPilchard as much as you want, but their point still stands. You have to do a fair amount of "reverse engineering" and black box testing whenever dealing with the Windows API as the MSDN documentation is insufficient.
Can't believe you were dugg down. That is the most accurate analogy I have ever seen."hmm lets waste time reverse engineering windoze crappy Internet Exploder so we can write buggy spaghetti code more quickly."
Still not sold on Chrome. I have had it hang up on me twice in the first week, and one time it was when opening Gmail. Not using it any more (for now).I talked about it on my site <a class="user" href="http://www.mbceo.com">http://www.mbceo.com</a>
strictneinSep 23, 2008
Are you really looking for everyone who read the article to respond?
silverseraphSep 23, 2008
Immersed in Firefox plugins, anything else is another failure to browse...
gigaSep 23, 2008
Bury TheRealPilchard as much as you want, but their point still stands. You have to do a fair amount of "reverse engineering" and black box testing whenever dealing with the Windows API as the MSDN documentation is insufficient.
kirbymeisterSep 25, 2008
Oh yeah, the lack of a linux version is horrible... I really hope they port it soon.
slikstaSep 28, 2008
Can't believe you were dugg down. That is the most accurate analogy I have ever seen."hmm lets waste time reverse engineering windoze crappy Internet Exploder so we can write buggy spaghetti code more quickly."
wsbmllcFeb 9, 2009
Still not sold on Chrome. I have had it hang up on me twice in the first week, and one time it was when opening Gmail. Not using it any more (for now).I talked about it on my site <a class="user" href="http://www.mbceo.com">http://www.mbceo.com</a>