{"id":5177,"date":"2014-09-04T15:48:08","date_gmt":"2014-09-04T19:48:08","guid":{"rendered":"http:\/\/redmonk.com\/sogrady\/?p=5177"},"modified":"2014-09-05T11:13:02","modified_gmt":"2014-09-05T15:13:02","slug":"fragmentation-pendulum","status":"publish","type":"post","link":"https:\/\/redmonk.com\/sogrady\/2014\/09\/04\/fragmentation-pendulum\/","title":{"rendered":"A Swing of the Pendulum: Are Fragmentation&#8217;s Days Numbered?"},"content":{"rendered":"<p><a href=\"https:\/\/www.flickr.com\/photos\/adc\/7925519\" title=\"Foucault&#x27;s Pendulum by alex de carvalho, on Flickr\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/farm1.staticflickr.com\/8\/7925519_a89daccdc9.jpg\" width=\"500\" height=\"375\" alt=\"Foucault&#x27;s Pendulum\"><\/a><\/p>\n<p>One of the lessons that has stayed with me all these years removed from my History major is the pendulum theory. In short, it asserts that history typically moves within a pendulum&#8217;s arc: first swinging in one direction, then returning towards the other. I&#8217;ve been thinking about this quite a bit in recent months as the predictable result of widespread developer empowerment becomes more and more visible in virtually all of the metrics we track. Unsurprisingly, when you have two populations making decisions, the larger one leads to a wider array of outcomes. CIOs, as an example, were long content to consolidate on a limited number of runtimes &#8211; Java, .NET and a few others. All of the data we see, however, suggests that as the New Kingmakers have begun to rise up and act on their own initiative, the distribution of runtimes employed has exploded. The pendulum, quite obviously, had swung from centralized to fragmented, driven by a fundamental shift in the way that technologies were selected.<br \/>\nThe question I&#8217;ve been pondering is simple: when does it begin to swing back in the other direction?<\/p>\n<p>If there is any reversal here, it will come from developers. Even the large, CIO-centric incumbents are aware today that developers are in charge, so there&#8217;s no evidence to suggest that CIOs have a plausible strategy for putting developers back under thumb. But while over the last few years newly empowered developers have shown an insatiable appetite for new technologies, it hasn&#8217;t been clear that this trajectory was sustainable longer term.<\/p>\n<p>Which is I&#8217;ve been paying attention, looking for evidence that the pendulum swing might be slowing &#8211; even reversing. The data is inconclusive. As Donnie has noted, there <a href=\"http:\/\/redmonk.com\/dberkholz\/2014\/05\/02\/github-language-trends-and-the-fragmenting-landscape\/?utm_content=bufferae1b9&amp;utm_medium=social&amp;utm_source=twitter.com&amp;utm_campaign=buffer\">have only been five languages<\/a> that really mattered on a volume basis on Github: JavaScript, Ruby, Java, PHP, and Python. And yet <a href=\"http:\/\/redmonk.com\/sogrady\/2014\/06\/13\/language-rankings-6-14\/\">our rankings<\/a> indicate that while they do indeed represent the fat part of the tail, there is substantial, ongoing volume usage of maybe twenty to thirty on top of that.<\/p>\n<p>What the data won&#8217;t say, however, developers themselves will. Witness this piece from <a href=\"https:\/\/www.tbray.org\/ongoing\/When\/201x\/2014\/07\/17\/Discouraged-Developer\">Tim Bray<\/a>:<\/p>\n<blockquote><p>\n  There is a re\u00adal cost to this con\u00adtin\u00adu\u00adous widen\u00ading of the base of knowl\u00adedge a de\u00advel\u00adop\u00ader has to have to re\u00admain rel\u00ade\u00advan\u00adt. One of today\u2019s buz\u00adzwords is \u201cfull-stack developer\u201d. Which sounds good, but there\u2019s a lit\u00adtle guy in the back of my mind scream\u00ading \u201cYou mean I have to know Gra\u00addle in\u00adter\u00adnals and ListView fail\u00adure modes and NSMan\u00adagedOb\u00adject quirks and Em\u00adber con\u00adtain\u00aders and the Ac\u00adtor mod\u00adel and what in\u00adter\u00adface{} means in Go and Dock\u00ader sup\u00adport vari\u00ada\u00adtion in Cloud provider\u00ads? Color me sus\u00adpi\u00adcious.\n<\/p><\/blockquote>\n<p>Which links to this piece by <a href=\"https:\/\/the-pastry-box-project.net\/ed-finkler\/2014-july-6\">Ed Finkler<\/a>:<\/p>\n<blockquote><p>\n  My tolerance for learning curves grows smaller every day. New technologies, once exciting for the sake of newness, now seem like hassles. I\u2019m less and less tolerant of hokey marketing filled with superlatives. I value stability and clarity.\n<\/p><\/blockquote>\n<p>Which elicited this reponse from <a href=\"http:\/\/www.marco.org\/2014\/07\/11\/developers-dystopian-future\">Marco Arment<\/a>:<\/p>\n<blockquote><p>\n  I feel the same way, and it\u2019s one of the reasons I\u2019ve lost almost all interest in being a web developer. The client-side app world is much more stable, favoring deep knowledge of infrequent changes over the constant barrage of new, not necessarily better but at least different technologies, libraries, frameworks, techniques, and methodologies that burden professional web development.\n<\/p><\/blockquote>\n<p>Which in turn prompted a response from <a href=\"http:\/\/mattgemmell.com\/confessions-of-an-ex-developer\/\">Matt Gemmell<\/a> entitled &#8220;Confessions of an Ex-Developer&#8221;:<\/p>\n<blockquote><p>\n  I\u2019m glad there are no compilers (visible) in my life. I\u2019m also glad that I can view the WWDC keynote as a tourist, without any approaching tension headache as I think about what I\u2019ll need to add, or change, or remove. I can drift languidly along on the slow-moving current of the everyday web, indulging an old habit when a rainy evening comes by.<\/p>\n<p>  It\u2019s a profoundly relaxing thing to be able to observe the technology industry without being invested in it. I\u2019m glad I\u2019m not making software anymore.\n<\/p><\/blockquote>\n<p>To be clear, these are merely four developers. Four experienced developers, more importantly. It may very well be that their experiences are nothing more than a natural and understandable change in priorities that comes with age.<\/p>\n<p>But their experience seems to mirror a logical reaction to a very rapid set of transformations in this industry. Given the hypothesis that the furious rate of change and creation in technology will at some point hit a point of diminishing returns, then become actively counterproductive, it follows that these could merely be the bleeding edge of a more active backlash against complexity. Developers have historically had an insatiable appetite for new technology, but it could be that we&#8217;re approaching the too-much-of-a-good-thing stage. In which case, the logical outcome will be a gradual slowing of fragmentation followed by gradual consolidation. Market outcomes would be dependent on individual differences between rates of change, the negative impacts of fragmentation and so on.<\/p>\n<p>It may be difficult to conceive of a return to a more simple environment, but remember that the Cambrian explosion the current rate of innovation is often compared to was itself very brief &#8211; in geologic terms, at least. Unnatural rates of change are by definition unnatural, and therefore difficult to sustain over time. It is doubtful that we&#8217;ll ever see a return to the radically more simple environment created by the early software giants, but it&#8217;s likely that we&#8217;ll see dramatically fewer popular options per category.<\/p>\n<p>Whether we&#8217;re reaching apex of the swing towards fragmentation is debatable, less so is the fact that the pendulum will swing the other way eventually. It&#8217;s not a matter of if, but when.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>One of the lessons that has stayed with me all these years removed from my History major is the pendulum theory. In short, it asserts that history typically moves within a pendulum&#8217;s arc: first swinging in one direction, then returning towards the other. I&#8217;ve been thinking about this quite a bit in recent months as<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spay_email":"","footnotes":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false},"categories":[72],"tags":[],"class_list":["post-5177","post","type-post","status-publish","format-standard","hentry","category-programming-languages"],"jetpack_featured_media_url":"","jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/redmonk.com\/sogrady\/wp-json\/wp\/v2\/posts\/5177","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/redmonk.com\/sogrady\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/redmonk.com\/sogrady\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/redmonk.com\/sogrady\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/redmonk.com\/sogrady\/wp-json\/wp\/v2\/comments?post=5177"}],"version-history":[{"count":0,"href":"https:\/\/redmonk.com\/sogrady\/wp-json\/wp\/v2\/posts\/5177\/revisions"}],"wp:attachment":[{"href":"https:\/\/redmonk.com\/sogrady\/wp-json\/wp\/v2\/media?parent=5177"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/redmonk.com\/sogrady\/wp-json\/wp\/v2\/categories?post=5177"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/redmonk.com\/sogrady\/wp-json\/wp\/v2\/tags?post=5177"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}