Hacker News new | comments | show | ask | jobs | submit login

These three activities have different QoS constraints: "voice" data is real time, lossy, and therefore has hardware assisted compression and routing; text messages and data are non-lossy, but have drastically different timing and retry constraints. So, even if they "traveled through the same towers and pipes" (they don't, a detail more expanded on by mdasen in his comment), it wouldn't make sense to charge the same for them as they have different cost requirements (although it might be somewhat more equal than it is now; in particular, text messages, which occupy valuable and limited control channel space, would likely become cheaper).

So it's UDP vs TCP? And why can't these be going over the same pipes?

A) "So it's UDP vs TCP" <- no... you should read up on "QoS"

B) "why can't" <- I did not claim they cannot... I stated that they don't (they don't even use the same frequencies in the air), and that even if they did, you wouldn't charge the same due to the QoS differences.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact