A disagreement between two individuals should be initially communicated between those two and ideally resolved privately. Hopefully both sides have enough empathy to understand the other's perspective to reach an amicable conclusion.
Airing out on Twitter as a first response (not sure if that's what happened here) is a sign of immaturity and not what someone does if their goal is to fix the original concern. By airing it out on Twitter, you put the other person on the defensive and they're less inclined to actually help you to resolve the original complaint.
Airing it out on Twitter is an escalation, and a decent outlet for escalating issues that are systematic and/or can't be resolved through other communication channels.
You're confusing CPU and memory pressure, and attributing blame to the wrong component.
Android's lack of smoothness is due to thread contention, whereas the iOS kernel uses a dedicated UI thread running at high priority. RAM size has no impact on UI performance, beyond a sufficient amount for the kernel.
I'm sorry you've had poor experience with Linux, I've had plenty of them myself.
I'm tired of dealing with ACPI / driver issues as well. That's why now I just buy ThinkPad and Intel-only chipsets. If you're going to use Linux, you have to research your hardware ahead of time (e.g. poor Atom support) or buy Linux laptops (Dell Ubuntu series, unofficially ThinkPad series).
I'm not trying to say everything's happy in Linux land. Printers are still a sore point, as are AMD / nvidia cards (Open or binary drivers? Multi-monitor support?).
This illustrates another pain point for Apple: the inability to change default applications.
Say Google releases a maps app for iPhone. Every time you get an address in a text, email, Facebook, Yelp, etc it's going to open up in Apple Maps requiring you to manually copy/paste everything in another app.
htop (and by extension top) is for CPU / memory / load information only.
Normally to get network and disk stats I have to run a combination of dstat, iotop. A simple screenshot comparison: http://i.imgur.com/eQPuQ.png
OTOH htop takes up ~2MB per instance, while glances is taking up ~13MB. Glances also doesn't have the ability to sort by columns except by CPU/mem %. You can't kill browse or kill processes from the list either.
To relate this to tech, there was an earlier study done that showed progress bars that updated in smaller increments (~1% steps) felt faster to end users than larger increments (20% steps) even though the time for the smaller increment progress bar to finish the task was the same or longer.
In other words it's reinforcing the primary argument of the article, the perception of waiting is more important than actual wait time.
Ad-free and FOSS: https://github.com/iSoron/uhabits