First of all, in the olden day the .Mac "homepage" did't seem to be case sensitive, as in: homepage.mac.com/user will get you to the same place as /User. iWeb is a bit pickier, as a wedding site I'm working on lives at web.mac.com/myuser/iWeb/Wedding/, but /wedding/ will result in a 404 error. Yes, a friend already reminded me that "Unix = case sensitive," but I don't care. While this could be labeled a minor complaint, my fiance and I have plenty of family members who aren't too hip on these computer thingies. They're going to get confused by something silly and minor like this, and I'm sure our relatives aren't the only ones.
Next on my list is the URL scheme itself. web.mac.com/user/iWeb/sitename? Could that get any less friendly? Granted "homepage.mac.com" might seems a little unprofessional to some, but this new scheme feels pretty cumbersome and just plain ugly. Why couldn't we simply have web.mac.com/user and web.mac.com/user/othersites, Apple?
Last but not least is how the new sites are organized in a user's iDisk. Old homepage sites still live in iDisk/Sites/, while shiny new iWeb sites live in iDisk/Web/Sites/iWeb/sitename. Nevermind a discussion about how needlessly buried that file structure is - I'm sure this dichotomy of old/new sites and content is going to confuse plenty of .Mac customers if they ever want to get at any of those files, or make a backup of their sites or entire iDisk.
But enough about my gripes, what do you guys think: do iWeb and its underpinning .Mac support have more issues besides CSS and standards? Let's hear your thoughts.