Read more.The likes of Microsoft, Mozilla and Opera are set to face another big-name threat with the impending launch of Google Chrome.
Read more.The likes of Microsoft, Mozilla and Opera are set to face another big-name threat with the impending launch of Google Chrome.
What rendering engine does it use?
If it's a 'new' one with enough nuances compared to Gecko/Opera/IE, developers just gone one more headache to deal with.
Personally I'm looking forward to the sad smiley dead tab indicator. Should be interesting!
this is actually quite good, i was very skeptical at first thinking woo, yet another rendition of Konquer, the only fools stupid enough to run that are apple users. Wheres the new features.
But it actually seams to have new stuff, the javascript engine multithreading, the full isolation between tabs. Could be very good, a big problem lots of the browsers have is leaking, often via javascript. If you keep opening lots of tabs, then close some open more up you find you get fragmented memory too. A certain popular browser seamed to keep all the memory in ONE HEAP until lately, meaning that it never got compacted.... Muppets. Not to mention the security implications.
This could really be a step in the right direction, will be intresting to see how the others react.
throw new ArgumentException (String, String, Exception)
An amazing amount of apps are still written in C++ with toolkits, i was always amazed by how MFC took off (i was never a fan, don't know if i was just been a luddite, but i didn't much care for it).
Now given that the vast majority of this app is rendering, rather than GUI per say, i think they will of had to primative languages and techniques for speed, rendering some declarative langauge via a declartative framework (say WPF) would be very slow. Easy to write but slow.
throw new ArgumentException (String, String, Exception)
I'd change that to: Easy to write when the tools work. But yes, it's slow as heck (but improving) right now.
We use mfc, forms and wpf - just pick the right one for the right job. I don't see why you have to go down one path abandoning all others. Certainly WPF represents the most probable MS future but it's got a lot of growing up to do. I can't stress 'a lot' quite enough as I head off to delete my .suo file so i can actually reload my solution.
but that's the thing. the renderer already exists - it's kde/apple's webkit. what google are doing is injecting a new javascript JITter, and some clever process manglement. there's no need to do the UI candy in something as vile as MFC is there?
and there's also the whole "multi-platform" thing. MFC? i mean, they use wine'd mfc to make picasa cross-platform, but i doubt that would cut it for a browser.
i wasn't meaning to suggest for a second that they would of used that!
if they've been remotely good, a company the size of google can, and should be able to afford to localise the app to each platform extensivly. Take advantage of text rendering/smoothing techniques local to that OS, ensure that your dialogue boxes match the look and feal (having OK,Cancel,Apply on win etc).
I'd of also hoped that they've really worked on the webkit, because last time i used konquer, it really did badly.
throw new ArgumentException (String, String, Exception)
There are currently 1 users browsing this thread. (0 members and 1 guests)