Previously, I wrote about Publishing to npm Using AppVeyor. This is a similar post, but specifically geared toward publishing an npm pack...AppVeyor npm MyGet
World Wide Web, that’s what the “www” stands for in www.rimdev.io - a show of hands for those who knew that?
It’s a relic from the days of 56k modems and the golden age of AOL when we had to explain the internet. When you could walk away from your computer, get coffee, have breakfast, come back and the page at the end that domain name might be loaded.
Antiques are fun to collect, and in today’s culture, use ironically, but we don’t wait for milk to be delivered, we don’t have a chunk of ice delivered for the ice box? If you’re Apple, you don’t even use USB Type-B. Anyone remember USB Type-A? No, you don’t! That’s the point.
We’ve gone through over a decade of innovation in hardware, software, the internet of things, but we can’t let go of a standard introduced by Sir Tim Berners-Lee in the world’s first web page in the late 1980’s. Even in it’s introduction, Berners-Lee quickly abbreviated www to W3, which would become the World Wide Web Consortium, or W3C, the curators of modern web standards. Special thanks to Jeffrey Zeldman for pointing out web standards to the internet with Desiging with Web Standards (you can also grab his free book Taking your talent to the web). So why do we persist?
The internet seems to cling to the antiquity that is the www prefix?
No. We’ve been building resilient re-directs for years! With very few exceptions, dropping the www will get you to the same domain. Type
google.com and magically
www.google.com is the link that appears.
We actively plan for this scenario, redirecting to the www prefixed domain. Why? Is it because no one will realize they’re on the world wide web, …er, internet?
The short answer is progress. The long answer; you’re actually going to a sub-domain of the main website. Any other instance of this practice is generally frowned upon. A sub-domain is treated, in any other case, as an entirely different website (and you’re fracturing your SEO). The early mobile practice of
m.yourwebsite.com has since been corrected thanks to responsive web design.
m was the sub-domain you were re-directed to when a mobile browser was detected. Why? Bandwidth and processors. Mobile devices weren’t as powerful as your desktop or laptop, nor where cellular networks. Once again, this practice has mostly been abandoned as cellular networks improved and devices rival desktop and laptop experiences. Why is the www is still with us?
Developers: Stop redirecting to www, actively fight against it.
Internet: Stop referring to www, stop typing www, it won’t break you.