Domain: manu-j.com
Stories and comments across the archive that link to manu-j.com.
Comments · 8
-
Re:None of this would've happened...
Speaking as someone who has to deal with 64 bit flash on linux
this was hard once, but then we got nspluginwrapper to make it easy. Then Adobe released 64 bit flash "beta" for linux (works better than many of the released versions that have passed, AFAICT) and now it's super easy. But since the iPhone doesn't come in different flavors like that (yet?) then you're not going to have that same kind of problem. Consequently, 64 bit flash is a red herring. Stop it.
Apps running using native platform tools do fairly well, cross-platform apps suck a lot of the time. You windows users have seen this too -- itunes, quicktime and safari are dogs on windows because they had to import all their own libraries.
So you're saying that because Apple is bad at cross-platform, it's a bad idea? As far as I can tell, you've offered only evidence of Apple's incompetence.
On Apple machines these are lighweight apps that are fast.
Go on, pull the other one. On Apple machines, iTunes and Quicktime are both still chunky and funky. Safari is pretty speedy, though it is not as speedy as WebKit on Linux . Or in other words, it's not really that fast. It's slower than the performance-oriented competition. Hell, it's slower than what it's based on. I consider that a failure. Apple does NOT write small, efficient applications for most any purpose.
And let's face it, as nice as open software is, working well is what sells units, ideology is secondary.
Bullshit. Polish is what sells units. Apple's stuff is shinier. But there's plenty of room for a backlash when users find that all the apps they want are on all the other phones, and the only one who doesn't have 'em is the iPhone. Give it a year and this will start to happen.
-
Re:Javascript performance
My javascript performance comparison between Firefox 3.6 and Chrome and Safari http://www.manu-j.com/blog/firefox-3-6-vs-chrome-vs-safari-javascript-performance/432/
As usual, Firefox performance on the v8 benchmark is pathetic where Chrome is more than 10 times faster.It is 24% faster than version 3.5.4 in V8 but it is clearly not enough. In the sunspider test, chrome is 2 times as fast as firefox. In this test, 3.6 is 17% faster than 3.5.4. Safari too comfortably beats Firefox in both these benchmarks
They should use Slashdot for testing JS performance. Click "Read More" to load a new discussion, then hit "Reply to This", type a response, hit "Preview", and count how many seconds it takes before you see the preview. May the best browser win!
-
Javascript performanceMy javascript performance comparison between Firefox 3.6 and Chrome and Safari http://www.manu-j.com/blog/firefox-3-6-vs-chrome-vs-safari-javascript-performance/432/
As usual, Firefox performance on the v8 benchmark is pathetic where Chrome is more than 10 times faster.It is 24% faster than version 3.5.4 in V8 but it is clearly not enough. In the sunspider test, chrome is 2 times as fast as firefox. In this test, 3.6 is 17% faster than 3.5.4. Safari too comfortably beats Firefox in both these benchmarks
-
Depending on the Country you're residing
I'd suggest you pick the best DNS from http://www.manu-j.com/blog/opendns-alternative-google-dns-rocks/403/ or http://www.dnsserverlist.org/indexbeta.php?oby=Q_RTT depending on the Country you're residing.
-
Re:Wha...?
I have been following chrome for mac development closely on my blog with weekly updates. Here is a list of the functionality as of Build 17426
What Works
* Almost All Websites
* Bookmark pages
* Most visited sites
* Open link in new tab
* Open new tabs
* Omnibox
* Back, Forward, Reload
* Open link in new window
* Drag a tab to make a window
* Launch new tab
* Cut, Copy, Paste
* Keyboard shortcuts
* about:version, about:dns, about:crash, about:histograms
* Find in page
* History with search
* Form Fill
* Delete Thumbnail in New Tab Page
* Window Positions Remembered
* View Source with synatx highlighting and clickable links
What Doesn't Work
* Plugins (No flash -> No youtube)
* Bookmarks Bar
* Print
* about:network, about:memory
* Web Inspector
* Input methods such as Kotoeri (Japanese)
* Preferences (Partial implementation)
* Full Screen Browsing
* Favicon (thanks brin) -
Re:Safari does clean up after itself.
Anyway, chrome beta is coming on nicely and hopefully I will be able to ditch safari for good. [Firefox is my main browser but I do need a second browser].
I have been keeping track of mac chrome and in the last two months it has become quite stable and only thing missing is flash. Some here would even consider that a feature. -
Re:Windows Only
There dare daily builds available for all platforms here http://build.chromium.org/buildbot/snapshots/ For the mac build, to get an idea about what status it is in and what works and what doesn't you can see my post on it http://www.manu-j.com/blog/download-updated-native-google-chrome-for-mac-os-x/230/
-
Re:How about actually getting the mac version out?
Chromium (the open source basis for Chrome) is available to download and compile, and you can also download unofficial binaries if you're really dying to see how Chrome for OS X is coming along.
And if you want to experience what a one-process-per-tab feels like on the Mac, you can check out the Chrome-inspired OS X browser, Stainless.