Comments on: Chrome-on-Mac precursor rough but workable
The development project underlying Chrome for the Mac is buggy, but CNET News' Stephen Shankland is cautiously impressed with the progress thus far.
The development project underlying Chrome for the Mac is buggy, but CNET News' Stephen Shankland is cautiously impressed with the progress thus far.
Say No to boxed software! The future of applications is online delivery and access. Software is passé. Webware is the new way to get things done.
Add this feed to your online news reader
Web sites launch all the time, but they also shut their doors. We highlight 15 that bit the dust this year.
Let the debate begin: Was the iPhone more important than iTunes? Was anything bigger than Google finding a great business model? CNET offers its list of the 10 most important stories of the '00s.
although its buggy...
i love this! :D
Still, to go the route of sticking with the "Apple interface", it is losing a little bit of browser space.
(Not that your average person will really care, though)
Also, i can't wait for HTML5s Local Storage, and generally just HTML5.
Hopefully Microsoft won't stay behind (as usual) and buckle the adoption of it.
Please Microsoft! Pretty please?
But JavaScript is important, and I was surprised how poorly Firefox's JavaScript fared compared to Chrome and Safari on the Mac.
In a perfect world they might have had more programmers for the Mac and Linux versions, but even Google's giant bucket of money only goes so far, and software engineering is one of those challenges notorious for not getting much faster when you throw more bodies at it.
Safari (and WebKit more broadly) became more intriguing to me once Apple decided to bring it out of its comfortable Mac OS X niche into the big, scary, chaotic world of Windows. Say what you will about Mac vs PC, but being available on Windows means exposure to a lot more users.
That said, I'll try to give Stainless a whirl soon.
I think a big part of it is that Mac users (not to start any kind of flame war) tend to be more tech savvy than the majority of Windows users. Yes there are less of them but they are probably more likely to try a new browser than your average Windows user.
They should think of a way to market their browser and leave M$ alone. Cnet is one of the reason they are not doing well. Lol. They are oneof the reason why mac is over hyped. One thing is for sure... They have tried their best to see M$ fall with biased articles and M$ reacted with windows 7.
Opera is my alternative browser IE and opera are my favourites. I used linux and its a joke no wonder its free and only less than 1 percent care world wide. I used the mac and i will say peopleare truely brainwashed. anyway mac is my alternative but i will only use it if microsoft stops existing.
http://my.opera.com/core/blog/2009/02/04/carakan
I'm not sure how buggy the Mac version is, but I don't really care as I am not a Mac user. But for Windows, I can't use any other browser! Chrome opens up in under 3 seconds, it never crashes, it never annoys me with updates and pop ups like Firefox, and the search/address bar built into one another is one of the greatest things I've ever seen a browser have and I see no flaws in "privacy", what this article mentioned was a flaw. If the person is looking up anything inappropriate in the first place, the user can go into Incognito mode, something not even mentioned in this article, and all their browser history, cache, sessions, and cookies is deleted once the incognito Window closes. So no, this article has it all wrong on those grounds.
Regarding CNet's charts, I find it disgusting that the Great Google Chrome can be matched up at all against Safari. Safari is absolute garbage for a web browser. The speed is nice, but the browser is broken, it follows no standards, the fonts are ugly, and it favors too much Mac garbage including the ugly Mac interface for it's browser window on Windows. Not everyone finds Mac stuff elegant and sophisticated.
If your a Firefox user even, Chrome is better. Firefox has gone down hill since the release of Firefox 3.0. Now they even want to throw out tabbed browsing and introduce something similar to the iTunes interface. How disgusting and disappointing from what once was the best web browser.
Less testing and development for browser specific fixes. I'm tried of people whining that function xyz doesn't work on their particular browser with a particular plug in. So much time is wasted chasing after all these little setups. It was painful enough just developing for IE and firefox without throwing chrome into the mix. For now I can ignore opera, konquerer and safari (which ticks off my fanboi manager to no end) because there are so few of them in our user pool that it doesn't matter. If chrome reigns supreme thats fine as long as it totally dominates and not take 30% of the share because that would be the worse case scenario....from a developers perspective.
Opera: 100/100 very fast.
Safari: 100/100 fast
FireFox: Failure.
Chrome: Failure
iE8: failure. (could not even read the results)
If you're curious about tracking how well the Chrome engineers handle this issue, I recommend you star the two following Chrome issues:
Acid3 fails on Chrome:
http://code.google.com/p/chromium/issues/detail?id=231
Acid3 Linktest fails on Chrome:
http://code.google.com/p/chromium/issues/detail?id=6208
It's built on the Safari engine, and Safari is light years ahead of chrome.
I downloaded the latest chrome release this morning specifically for the acid3 test. Chrome failed.
As I said above, for both Chromium on Mac and Chrome on Windows, I got 100/100 on Acid3, but linktest failed. And to reiterate, here are the bugs if you want to track them.
Acid3 fails on Chrome:
http://code.google.com/p/chromium/issues/detail?id=231
Acid3 Linktest fails on Chrome:
http://code.google.com/p/chromium/issues/detail?id=6208
From Google Code Chromium Wiki
Prerequisites
* An Intel Mac running Mac OS X 10.5 (?Leopard?). V8 does not currently support PowerPC.
more resources, http://www.webstandards.org/
- by topgunb2 May 12, 2009 3:29 PM PDT
- mac itself is buggy, why blame poor chrome
- Like this Reply to this comment
-
Showing 1 of 2 pages (40 Comments)