I hardly consider myself an expert ARM ASM programmer (or even an amateur...), but a baseline level of how to read it even if you have to look up a bunch of instructions every time can be super useful for performance work, especially if you have the abstract computer engineering know how to back it up.
For example, it turns out that gcc 7.3 (for arm64) doesn't optimize
foo() ? bar() : baz();
the same as
if (foo()) {
bar();
} else {
baz();
}
!
The former was compiled into a branchless set of instructions, while the latter had a branch!
I'd argue Jobs mostly kept Ive under control. Tim Cook let him go nuts (didn't act as an editor) until it was finally seriously hurting the business (butterfly keyboard era) and went in the complete opposite direction by firing him.
I never met Steve. I met Cook and on a separate occasion Forstall. Cook always struck me as a shy business bean counter. Forstall is an engineer through and through. Such a shame we never got to experience an alternate timeline where Apple was under his leadership.
I think Ive has burn out issue at the time and has clearly thought about departing Apple. ( A book chronicling 20 years of Apple's design in 2015 ) He wanted to design the perfect and final thing and so MBP was rushed. Steve Jobs would have worked him and likely said hey this is good but we must do it incrementally so our user can adopt to changed. How about the Keyboard keys goes to 1.2mm instead of straight to 0.7mm key travel.
It took us 20 years for humans to adopt from the good old 2.5mm keyboard to 1.5mm. And you want to cut in half again in one go?
I think it is best summarised as Steve Job's quote in the movie;
"Musicians play their instruments. I play the orchestra."
I gotta be honest, I really feel like these comments are completely divorced from reality.
No one (p99.99) wants to get rid of Google/Apple on their phones. But "how do I install Play services" is a wildly popular search for people who own Kindle Fires.
No one wants to deal with the Windows 98ificaiton of phones.
> I gotta be honest, I really feel like these comments are completely divorced from reality.
> No one (p99.99) wants to get rid of Google/Apple on their phones. But "how do I install Play services" is a wildly popular search for people who own Kindle Fires.
Just like no one wants to get rid of Internet Explorer, right?
No one wants to, in large part because it's a fucking nightmare. I say that as someone who not only knows how, but knows how to write the code for it too. Why is it so hard? What makes it a nightmare? Their business model requires a walled garden, because otherwise...
Anyways, People have no issues migrating from myspace to facebook, or from youtube to instagram to tiktok. If it wasn't a fucking nightmare full of bullshit, user hostile rules (e.g. manifest version, or max age of TCP connections) there'd be a market for Google alternatives.
Right now the only motivation is privacy, and Graphiene works pretty well. Turns out, caring about privacy is a lot more motivating than wanting some feahure to work. Especially when "they" have a vested interest in making sure no one else can provide that feature.
You probably simply don't know what this is about. When Android phones "age" to a certain point, they become locked (user cannot log into the OS), and the only way to circumvent this is by jailbreaking them and installing a different firmware / OS.
I have a Galaxy S7 that is in this condition, and I haven't the time to try to reinstall it.
Many users never face this problem because they buy new phones before their old ones hit this particular point, often because many applications will stop working before that due to developers discontinuing support effectively rendering the phone useless. I ran into this problem because I kept my phone around due to some images stored on it (well, now that's lost forever).
I know this requires changing the SoC to x86_64 or ARM but I want bog standard Linux any distribution to run on the cell phone, at least run in the sense of the kernel. The applications would be up to the distribution maintainers. Talking to the modem should just be a Linux kernel module that has been blessed by Linus Torvalds. The code must be clean enough that at no point is he tempted to raise the middle finger or start writing an email. No obfuscated code, no lawful intercept JTAG debugging code, no dodgy BIOS just bog standard Linux and standard x86_64 or ARM hardware. Maybe something like coreboot as the BIOS.
In fairness I also want a goose that lays golden eggs.
Nobody wants that because there's currently no market for it, so no solutions for it.
(And yes, we can quibble about alternate Android app stores in countries that aren't China, but Google's rigged that game heavily in their favor via defaults)
I hardly consider myself an expert ARM ASM programmer (or even an amateur...), but a baseline level of how to read it even if you have to look up a bunch of instructions every time can be super useful for performance work, especially if you have the abstract computer engineering know how to back it up.
For example, it turns out that gcc 7.3 (for arm64) doesn't optimize
the same as !The former was compiled into a branchless set of instructions, while the latter had a branch!