#SaphireLike, why/when would one prefer to use it, other than in legacy circumstances?
#Ruxtonit's just that a preference that hungover from legacy circumstance
#Ruxtonalso host separation.. if you want a separate host for www, you cant exactly make it non-www if you have other services tied to that domain name (think mail)
#Ruxtonthat limitation has again changed over time as more and more software and methodologies have been created
lmorchard685 joined the channel
#Ruxtonso the 90s config was mail on root of domain and mail., www. for websites.. then people,software and hardware got better/cheaper at routing things and SSL got the ability to have multiple host names and the no-www movement started
ShadowKyogre joined the channel; ShadowKyogre left the channel
#KartikPrabhuSaphire: I agree. I would like to be no-www but there is some technical redirection to my domain stuff from my domain name provider to the hosting thing which needs www
nickodd, rsheftel31521, [jgmac1106], [scojjac], hoschi and [Forest_Johnson] joined the channel
#[Forest_Johnson]I always thought you had to support both all the time. www and no www. cuz if you dont, you will accidentally murder some of your users
#[Forest_Johnson]thats what the corps do at least. Seems like a silly thing to argue about
#[Forest_Johnson]huh, I guess I never thought about re-directing. I guess for caching and what not it helps if theres only one URL for each page, but it doesn't have to be that way
#jackyeven then, a decent client should resolve the proper URL and use that
hoschi joined the channel
#alex11i know people defend google/chrome's decisions - or at least explain it - on the basis of 'they're an advertising company'