I'd rather my Mac were more reliable about getting on the net -- or if failures to do so were easier to fix and to understand.
Sometimes it takes fussing around (e.g., rebooting the cable modem, telling the Mac to try again to connect) to get on the net, and this time spent fussing around never seems to leads to an insight that would help the next time I need to fuss around.
It is a small thing, but this is one aspect of "client computing" where I would probably prefer the Linux way of doing things in which it is more tedious to do simple things, but when something goes wrong, it is easier to understand the problem.
Yeah, just yesterday I went to a local cafe and they'd changed the wireless password. I had to search online for a way to change the current password for a remembered wireless network! Turns out there's no way really, you have to run this wireless wizard thing and input the password that way. What?!
Yeah, I've never had problems with just changing it via the keychain. Also, manually connecting after it fails to connect causes it to prompt me for the password.
I did forget the network once, but no go. Also thought pw for wifi points would be accessible through the network prefs. I'll check keychain next time.
Sometimes it takes fussing around (e.g., rebooting the cable modem, telling the Mac to try again to connect) to get on the net, and this time spent fussing around never seems to leads to an insight that would help the next time I need to fuss around.
It is a small thing, but this is one aspect of "client computing" where I would probably prefer the Linux way of doing things in which it is more tedious to do simple things, but when something goes wrong, it is easier to understand the problem.