It's a browser!
I'm very pleased that it builds, and works without much fuss. I'm not quite sure whether it's capable of replacing Safari for now, but it's definitely a start (provided you download the 3 GB worth of source code). And here's what it looks like:
Rendering my blog
Good job there, though it isn't surprising as it's taking most of its rendering codebase from Webkit. It does a great job, keeping everything looking great in the process.
Acid3 Test
Apropos, it's an older version of Webkit. Newer ones are fully Acid3-compliant.
Home Screen
It seems like every browser is now coming with its very own 'home-screen'. Well, except Firefox (but there's probably a plugin) and IE.
V8 Benchmark
For reference, Webkit (build 5528.17, r44282) gets around 2,600 on the same hardware under OS X. V8 I guess is tricky to optimize on the Mac, and considering what its doing, I'm not surprised.
Processes
Now, I know what you might think, but it's actually not crashing, it's just that Chromium does not delegate CPU to inactive tabs (much), so it shows up as "Not responding". It'd be the same (sort of) if you ran any app from the Terminal, but backgrounded it. Also, make sure you understand how Activity Monitor and OS X calculate and handle virtual memory, before complaining.
Oopsies
Maybe they should've put a big TODO here, lol.
Other things that I noticed which aren't finished yet would include a lack of a status bar on the bottom (especially important for downloading things), and plugins such as Flash. It's interesting that the Mac Flash plugin wouldn't work.
In summary
I'm very happy to see that TONS of progress has been made on this project (seriously, I'm not being sarcastic). On Windows, I was blown away by the browser's capabilities and simplicity, and I suspect it will become my new browser of choice when it gets around to being officially released on the Mac.
Jeeze, I'm really tired of waiting for good FOSS projects!
0 comments :
Post a Comment