or Connect
New Posts  All Forums:

Posts by melgross

We've had a number of threads about this. Too bad you weren't there.So no, it's not just Safari. And there, it's not just RAM that's a problem. But when some of us run video editing, photo editing, and 3D CAD, performance is a big issue. More RAM allows bigger files to be used, and more of them.The same thing is true for games. Big, 3D games use a lot of RAM. Since the GPU shares RAM space, that limits not only CPU access, but GPU access. That means textures, normally held...
I keep saying that I'm going to join the developer program just to get my hands on Xcode and the betas, but I'm too busy, unfortunately.What I would like to have seen is memory compression, as we have it with Mavericks. It seems to work well enough, though it doesn't solve all the problems of too little RAM. But as no one has mentioned it for iOS, I'm assuming that it isn't there. It would have been interesting if it were, though I suppose Apple would have mentioned it...
I don't know why you are so shocked. This is a considerable decrease in performance advancement. I think that just admitting that will get us through a lot, and then we can get to talking about what Apple's thinking about this might be.I'm already seeing some early performance tests, and these phones aren't nearly as ahead of the newest competing phones as was Apple's 5 and 5S. With competing devices getting features that Apple isn't bothering with, performance is one...
Yes you can double transistors on a tick. It depends on what they are used for. A tock, Intel style, is a major architectural design change, and unless we get evidence of that from Anandtech when they get to do their usual very complete job, we can't say that Apple did that. Specialized execution units, if they aren't part of an architectural design change, are just additional units.As usual though, we'll never know what all those transistors will be for. We still don't...
Sorry, but I just have to disagree.Last year, along with the year before, they barely nudged to clock and achieved double the performance. While I didn't expect to see that again (though I kept my fingers crossed), I did expect to see 50% on the CPU, and 75% on the GPU, so yes, I'm disappointed.As for clock rate, I already went through that. There are two types of CPU designs. One sends two, maybe at most, three instructions at once, and needs, and uses, a high clock. The...
I don't remember it being said to have Desktop class performance. I remember them calling it a Desktop class chip, which isn't exactly the same thing.
What I meant was, and I should have been clearer, was would it convert an app that was specifically designed to use the features of one CPU family to take advantage of the very different features of another CPU family? This is where things get hung up. I saw plenty of software being described as "taking just a weekend" to port over, and seeing it on stage, but then not coming out for six to eight months afterwards, because of all the work that needed to be done after the...
Well, a lot of those "problems" aren't really problems. With such thin screens, the difference in light transmission would be negligible. The same thing is true for weight. We would be talking about several grams.
Some of the problems mentioned in Tim's article aren't exactly correct. A major one which I'll highlight is the cracking mode. The mode mentioned has to do with multi crystalline structures, where a scratch can open to a crack along crystal surfaces. But these are single crystal boules, just as with single crystal metals, this is much stronger. I think it still needs to be investigated. But phone design plays just as much into whether a screen will crack, as the material...
Yes, it does both, but will it recompile ARM to x86?, and visa versa?
New Posts  All Forums: