Separating api. and www. makes authentication messier (thus less secure). [At least I haven't seen a clear and good one yet.]

And with HTTP/2 you don't have to worry about static stuff slowing down or crowding out API req-resp data.

Exactly why don't you want your site's cookies to affect your site? Do you think perhaps you're abusing what cookies are meant to do?

> I actually love www subdomains - the origin tells you it is a website.

It lacks that connotation for the regular user.

I don't think so. Let's say you have one of the new TLDs for your site, say "new-york.florist", a nice domain. It's my belief that writing "new-work.florist" on your ads, business cards or merchandise will not let regular users know that it's a domain name. Writing www.new-york.florist will help indicate that this is your website.

Adding all the new TLDs have made the www prefix more useful than ever.

Let's say you have your business advertised on your vehicle.

Put www.somthing.com on there and it is obvious to most how to find your business online.

https:// is ugly and longer IMHO.

Wouldn't you place it next to some other contact details? A regular person can deduce it's a internet address.