{"id":7,"date":"2017-09-13T03:34:48","date_gmt":"2017-09-13T03:34:48","guid":{"rendered":"http:\/\/blogs.harvard.edu\/jacobajit\/?p=7"},"modified":"2017-09-13T03:34:48","modified_gmt":"2017-09-13T03:34:48","slug":"the-evolution-of-the-internet","status":"publish","type":"post","link":"https:\/\/archive.blogs.harvard.edu\/jacobajit\/2017\/09\/13\/the-evolution-of-the-internet\/","title":{"rendered":"&#8220;The Evolution of the Internet&#8221;"},"content":{"rendered":"<p>Last week, we collectively groaned as we learned about the struggles of creating a system of hardware and software that was seamlessly interoperable. Unfortunately, that story doesn&#8217;t change much as we move forward into the software implementation of host-to-host communication on the ARPANET. To be fair, standards and interoperability are something we still struggle with to this day. Why can&#8217;t you plug your iPhone&#8217;s USB-A cable into your MacBook&#8217;s USB-C port? (Props to Apple for adopting the Qi wireless standard charging protocol for the iPhone X announced today. As we were mentioning in our discussion, once a standard reaches a certain level of permeation, it&#8217;s difficult for a company to resist adoption.) If one company can&#8217;t maintain full interoperability within their suite of devices, it&#8217;s a miracle we managed to settle on fundamental protocols like IP at all.<\/p>\n<p>An interesting point from the reading was how much autonomy was granted to the select group of grad students who developed these communications protocols. Much of this was due to a lack of interest from the orthodoxy, but it turned out to be a blessing in disguise, allowing for bountiful experimentation and innovation. This seems to be a repeating case throughout history, where a lack of intervention can sometimes lead to the best outcomes. For example, the urban areas most targeted for renewal and removal of &#8220;blight&#8221; ironically became the most damaged from well-intentioned government efforts, while neighborhoods like Boston&#8217;s North End, left untouched, flourished organically. In the case of ARPANET, the lack of close supervision allowed for rapid evolution of the network in way unforeseen by the general establishment.<\/p>\n<p>As we touched on in our discussion, the freedom afforded to the developers of ARPANET also enabled the creation of a new set of cultural norms. Today, we still find ourself pioneering cultural norms on different platforms. How are &#8220;green texts&#8221; perceived compared to &#8220;blue texts&#8221; (iMessage&#8217;s subtle classification might have an intended effect)? What belongs on your Instagram, and what goes on your &#8220;finsta&#8221;? How does anonymity color our interactions with our peers, and does this anonymity give license to be offensive? Technology develops in tandem with society, with new use cases emerging organically initially, and eventually being integrated into products we use. When a critical mass began downloading Emoji fonts for use in messages, for example, companies were quick to integrate them closer with the OS, further implanting them in our cultural vocabulary.<\/p>\n<p>For those that do not adapt, however, demise seems to be a fairly inevitable conclusion. We mentioned DEC in our discussion, a company I should not recognize were it not for my readings of post-mortems. I was recently reading an Economist article on the company from 1984 in Lamont. The article described IBM&#8217;s embrace of personal computing contrasted with DEC&#8217;s reluctance to leave behind its familiar world of profitable minicomputers. While this may have been a smart short-term business decision by whoever analyzed the potential costs\/revenues, it&#8217;s clear that choices like this led to the company&#8217;s eventual downfall. When it comes to the internet and personal technology, those who do not move fast and break things tend to be broken themselves in no time.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Last week, we collectively groaned as we learned about the struggles of creating a system of hardware and software that was seamlessly interoperable. Unfortunately, that story doesn&#8217;t change much as we move forward into the software implementation of host-to-host communication on the ARPANET. To be fair, standards and interoperability are something we still struggle with [&hellip;]<\/p>\n","protected":false},"author":8863,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-7","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/archive.blogs.harvard.edu\/jacobajit\/wp-json\/wp\/v2\/posts\/7","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archive.blogs.harvard.edu\/jacobajit\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/archive.blogs.harvard.edu\/jacobajit\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/jacobajit\/wp-json\/wp\/v2\/users\/8863"}],"replies":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/jacobajit\/wp-json\/wp\/v2\/comments?post=7"}],"version-history":[{"count":1,"href":"https:\/\/archive.blogs.harvard.edu\/jacobajit\/wp-json\/wp\/v2\/posts\/7\/revisions"}],"predecessor-version":[{"id":8,"href":"https:\/\/archive.blogs.harvard.edu\/jacobajit\/wp-json\/wp\/v2\/posts\/7\/revisions\/8"}],"wp:attachment":[{"href":"https:\/\/archive.blogs.harvard.edu\/jacobajit\/wp-json\/wp\/v2\/media?parent=7"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/jacobajit\/wp-json\/wp\/v2\/categories?post=7"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/jacobajit\/wp-json\/wp\/v2\/tags?post=7"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}