1,496 karma · joined February 22, 2007
[ my public key: https://keybase.io/listic; my proof: https://keybase.io/listic/sigs/BfY38Sbck1eYRAOZZCfzYTQpVFB3DXW3GNLbx0WHMbU ]
I feel that today's phones are way too large, so I limit my choice to non-huge ones. So far, last year's Sony Z3 Compact tops the chart: 44% better battery life than iPhone6s in my 'heavy usage' scenario, 63% better in the default scenario. I'm eagerly awaiting the results for the recent Z5 Compact: it might provide even better battery life (72.5 hours compared to 'two and a half days', as tested by The Guardian [2] [3]).
[1] GSMArena: Battery life test results http://www.gsmarena.com/battery-test.php3
[2] The Guardian: Sony Xperia Z3 compact review http://www.theguardian.com/technology/2014/oct/03/sony-xperi...
[3] The Guardian: Sony Xperia Z5 Compact review http://www.theguardian.com/technology/2015/sep/23/sony-xperi...
I'll believe it when I'll see it. All we have is their word for it, and I really don't like the way they are promoting their product so far.
Do you actually turn it on manually every time?
What does the low power mode actually do?
* travel a lot. It doesn't have to be often - but when you leave your room early in the morning for a long day in a new town, and use it a lot, it really gives you peace of mind to know that you will be able to make that last important call in the evening.
* forget to plug it in. Seriously: do I really really have to plug this gadget in evry single evening? what if I forget or don't have the means to, every once in a while? It's a flagship device we're talking about; isn't it supposed to make my life easier?
* want your phone to have extra margin of reliability just in case - either to prolong its life when the battery deteriorates over time, or use it in cold weather - I am not sure if it's permanent damage, but battery holds less charge in the cold.
The iPhone is not the worst offender - it's probably slightly above average as far as smartphone battery life goes, but, to me, saying that battery life is not an issue sounds like a blasphemy: we (the consumers) have just squeezed barely adequate battery life from the manufacturers and voicing the opinion that it's enough feels like inviting back the compromises that they (the manufacturers) are far too happy to use.
The battery pack sure solves some woes, but it's not by coincidence we call it a mobile phone: it is supposed to be self-sufficient. Do you like to carry around a second box on your body at all times, just to be able to use a smartphone reliably? I don't. Battery pack should be a bonus that's nice to have, not a requirement to last through the day.
That reminds me: as an emebedded systems programmer, I've encountered a proper standards-compliant C compiler that allowed switching between a full, light and no version of printf() with a switch - you were allowed to omit just that one bit of the standard library for some significant savings in RAM and ROM usage. Of course, it was a little wonder for me at the time that a standards-compliant C compiler existed on that platform at all, but to realize that printf() function could often be the most heavy part of the application was another thing altogether... mind-expanding, really. The lesser C compiler vendors would just cut corners on the standard library implementation where they see fit, but that one left standard compliance as an option.
What is Apple's iPhone 6s release schedule?
Apparently, they have already released it in the countries other than the US, but I still can't see any information online regarding where it was released and where it's going to, next.
Wikipedia says [1] high capacity road can carry 2,400 passengers per hour; light rail 20,000 - 25,000 passengers per hour per lane in each direction.
[1] https://en.wikipedia.org/wiki/Light_rail#Comparison_with_hig...
Wikipedia article lists five operational systems like this in the world: https://en.wikipedia.org/wiki/Personal_rapid_transit#List_of...
Well, it's quite a reasonable engine for a target weight of 570 kg (1,250 lb), but with that weight I doubt it will go by as a motorcycle in any jusrsdiction, or will it, in the US?
Also, stated fuel efficiency happens to be 84 mpg-US highway, but only 60 mpg-US EPA blended, which is good, but not that surprising.
What is surprising though, is how did they managed to achieve great safety rating?
And what engine will it have? 84 MPG is very well acihevable in the smaller maxi-scooter category, e.g. Honda's PCX150 сlaims 100 MPG [1] for it, and it goes about 70 mph tops. Improving fairing is known to have a noticeable effect on mileage, on scooters, so I believe a car could do better.
[1] http://powersports.honda.com/2016/pcx/specifications.aspx
I actually expected the iPad Pro to support OS X apps; maybe via being powered by a new Apple Ax frankenchip that runs iOS ARM as well as x86 code (another payoff from the investment to custom chip design) and/or by requiring to recompile with the latest XCode for the App Store (a payoff from the long investment in LLVM).
Maybe next year.
btw, Magic: the Gathering debuted in 1993.
Maybe by chance you even have the source? It seems to have disappeared from the net, together with Gitorious, and the original author is unavailable.
To think again, shouldn't a modern C/C++ compiler be able to produce better code than this assembly without the intrinsic unportability? Let's take, e.g. SWAP
defcode "SWAP",4,,SWAP
pop %eax // swap top two elements on stack
pop %ebx
push %eax
push %ebx
NEXT
(and NEXT is) /* NEXT macro. */
.macro NEXT
lodsl
jmp *(%eax)
.endm
This won't really be blazing fast, or will it?> It's amazing how many new standard things came out of Diablo and Diablo II. [...] The rarity thing [for loot], for example, just kind of made sense.
While Diablo certainly helped popularize quite a few such features and even arguably gave birth to a genre (I heard people calling various other games a Diablo), it would be overconfident for them to claim inventing it: Magic the Gathering [1] had it years prior. There, rarity was implemented with printed pages: you print all your common cards on a Common sheet, uncommon cards on an Uncommon sheet and rare on Rare sheet; then put 1 card from Rare, 3 from Uncommon and 9 from Common into each booster pack. (not actual numbers! there are also Mythic Rares and each card has a tiny chance to be a Foil version, which complicates the situation, but the basic idea is something like that; from memory)
Same goes for the idea of a quest log: I don't have a specific example in mind, but I have a hard time believing no game had it before Diablo II.
[1] http://www.intel.com/content/www/us/en/smartphones/smartphon...
[2] http://www.intel.com/content/www/us/en/tablets/shop-tablets....