I think you meant to end that with "phone calls" rather than "to deliver SMS?" SS7 was used for that, but had a significant amount of idle time since most phone calls are much longer than the time needed to setup the connection.
I do indeed mean SMS, but I was focusing more on the air interface. There, SMS definitely consume resources in the same way that calls do (although of course at a very different rate: SDCCH uses 0.8 kbit/s, as opposed to 13 kbps for full rate voice/CSD traffic channels).
Because it dates to a time when such attacks were infeasible. GPS is very similar in that regard. Even HTTPS was uncommon back when I was in university. NASA spacecraft still communicate over unencrypted channels.
not just mindsets, but the computing power available. These days, my smartphone is millions of times more powerful and the computation to do TLS encryption on every website I visit is trivial for a computer that fits in the palm of my hand. Way back when, the 1 or 2 kilobytes or so a modern RSA private key (PEM format) would take up on disk was meaningful when you only had 4 megabytes of RAM and CPUs ran in the megahertz range.
Also to a dumb phone it doesn't matter whether an SMS contains a phishing link because it has no way of accessing it. Until the advent of smart phones SMS phishing was a non-issue.