1. drive aliases. Basically the file system in Windows sucks. There are a ton of cool file systems in unix land but unless you want to really break tons of stuff AFAIK you are stuck with NTFS on Windows, no journaling FS in 7 like MS promised.
WTF? NTFS has had journaling since it was introduced. (What, mid-90s?)
Maybe you're confusing NTFS with Fat32, except everything from Windows 2000 on has defaulted to NTFS on installed. I believe Win2k and XP can run from a Fat32 disk, but they don't like doing it... Vista and Windows 7 require NTFS to run.
2. Real multitasking. The amount of things that make Windows unresponsive is mind boggling. Pop in a CD/DVD, try and print, explore the network, etc. Okay if you must, make ONE thing unresponsive, don't kill my whole OS trying to find all the printers on the network. I have 4 CPU's and 4GB of RAM etc and it's SLOW!!! WTF!
When's the last time you used Windows? That complaint applied to Windows 95, 98 and ME. But it hasn't been true in a looong time.
What? Are you suggesting that my bank's website should verify whether I'm connecting over wifi vs. a wired connection, or a hub vs. a switch, etc. THEN decide whether to use SSL or not? Or perhaps I should have to remember to click a button when I'm on a potentially eavesdroppable connection?
SSL takes the right approach - if the information should be secure then encrypt it, regardless of whether it might possibly be somewhat secure by other means.
As far as the certificate infrastructure is set up, I'd go with an SSH-type system where everyone generates their own keys and the first time you connect you carefully confirm you connected to what you wanted to, but the central signing authority model does have some advantages, as well as disadvantages.
Surprise due today. Also the rent.
