You know always boasts about how powerful their A-Series chips in the iPhone/iPad are on paper.

But they never mention that you never get to use that power because of how restrictive is.

I just compiled the entire toolchain on the in under 10 minutes.

Would it take less on an iPhone? I cannot find out easily, Apple won't let me compile the Go toolchain on an iPhone.

That's why the is actually much more powerful than even the most recent .

@MatejLach since the Apple arm developer kit and the iPad pro have the same processor perhaps we'll learn soon enough?

@brion @MatejLach except for the part where the NDA on those dev kits prohibits folk from sharing benchmarks.

@nivex @brion @MatejLach Okay, but later this year when the non-dev-kit ARM Macs come out still counts as "soon enough".

@apetresc @brion @MatejLach Right. I parse the OPs post as the power comes not from the clock cycles but from the openness of the platform.

That said, there have been some leaked benchmarks:

@MatejLach the problem with open source advocates have here is why anyone would *care* how fast their phone could compile go, versus the things that they *do* care about on a phone (webshits, AR whatever, etc)

this is coming from someone who has an N900, but for my next phone, would probably buy an iPhone SE if i had to buy a new phone right now. (the difference being the N900 was a legitimately great phone beyond any linux stuff - i can't say the same for the freerunner, and i suspect it'll be the same for the pinephone...)
@MatejLach and i do care about this stuff, but you have to make the case, and when considering a phone, i tend to value "good at communications or taking pictures" over being able to build RPMs on the go. pragmatism in action...

I think it's the difference in expectations: do you want a pocket computer, or a phone?

@libc Sure. And that's fair. But any 4 year old Snapdragon is good enough for browsing Instagram. So when Apple talks about how you get this awesome CPU, brings up benchmarks comparing the competition etc. as if to justify the cost, but the sorts of things I may want to do with such a powerful machine in my pocket are impossible because of OS limitations, the question then becomes, why even bring up the CPU if in practice the PinePhone can do so much more with a much weaker CPU.

@libc Also the particular example I gave was more to illustrate that I'd rather have an OS that allows me to do things my way, if I want to, even if it's not something that I am likely do do often, because it's exactly those 'in a pinch'/'oh I forgot my laptop' moments where I'd rather be able to compile the Go toolchain than not.

It's that there's no assumptions from the OEM/OS about what I as a user should be allowed/not allowed to do with my own hardware with stuff like the

Sign in to participate in the conversation
Matej Lach's mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!