3 ms·
I was surprised how poorly it ran on my very modern phone. And then how tiny everything was on my desktop. When I looked past that and tried to draw a cat, it
by Waterluvian 10y ago
I was surprised how poorly it ran on my very modern phone. And then how tiny everything was on my desktop.
When I looked past that and tried to draw a cat, it wasn't all that useful. I mean cool, you saw I was drawing a face and gave me 50 options. But what am I supposed to do with that?
It feels like a rehash of what the Newton would do when you tried to draw stuff. But it does it better. I think if I could skip the "pick what I meant" step, it would be cool for whiteboarding in the office.
- sigmar 10y ago>I was surprised how poorly it ran on my very modern phone What phone and what browser? Ran great in chrome on my mid-range android.
- Waterluvian 10y agoSony Z3. Chrome.
- johansch 10y agoThat's because your very modern phone has a very puny CPU compared to even the average desktop CPU. I'm surprised about how few people know that their "2 GHz multi-core" phone is 5-10x slower than an average 5 year old desktop on common tasks. (Edit: hehe, as evidenced by this post being downvoted. The HN audience doesn't know any better either?)
- Waterluvian 10y agoI think it's more because you're making a straw man argument. Nobody disagrees that they're slower. I'm saying it's not enjoyable on my phone despite them saying it's good on phones.
- photojosh 10y agoProbably downvoted because you're wrong? (Not that I did.) But this is with the caveat that this is comparing a desktop Mac to an iPhone and I haven't the faintest clue about top Android phones, although I have the understanding that the A10 destroys the current Qualcomm SoCs. Here's an instructive article from last year comparing a 2013 Mac Pro and an iPhone 6s: https://www.mikeash.com/pyblog/friday-qa-2016-04-15-performance-comparisons-of-common-operations-2016-edition.html https://www.mikeash.com/pyblog/friday-qa-2016-04-15-performa... The relevant quote: >The most remarkable thing about this is how similar it looks to the Mac results above. Looking back at the old tests, the iPhone was orders of magnitude slower. An Objective-C message send, for example, was about 4.9ns on the Mac, but it took an eternity on the iPhone at nearly 200ns. A simple C++ virtual method call took a bit over a nanosecond on the Mac, but 80ns on the iPhone. A small malloc/free at around 50ns on the Mac took about 2 microseconds on the iPhone. >Comparing the two today, and things have clearly changed a lot in the mobile world. Most of these numbers are just slightly worse than the Mac numbers. Some are actually faster! For example, autorelease pools are substantially faster on the iPhone. I guess ARM64 is better at doing the stuff that the autorelease pool code does. >Reading and writing small files stands out as an area where the iPhone is substantially slower. The 16MB file tests are comparable to the Mac, but the iPhone takes nearly ten times longer for the 16-byte file tests. It appears that the iPhone's storage has excellent throughput but suffers somewhat in latency compared to the Mac's.